mirror of https://github.com/apache/druid.git
clarify granularity docs (#7977)
This commit is contained in:
parent
7a5bc5ffcd
commit
10d6b0318d
|
@ -176,11 +176,10 @@ If you change the granularity to `none`, you will get the same results as settin
|
|||
} ]
|
||||
```
|
||||
|
||||
Having a query granularity smaller than the ingestion granularity doesn't make sense,
|
||||
because information about that smaller granularity is not present in the indexed data.
|
||||
So, if the query granularity is smaller than the ingestion granularity, druid produces
|
||||
results that are equivalent to having set the query granularity to the ingestion granularity.
|
||||
See `queryGranularity` in [Ingestion Spec](../ingestion/ingestion-spec.html#granularityspec).
|
||||
Having a query time `granularity` that is smaller than the `queryGranularity` parameter set at
|
||||
[ingestion time]((../ingestion/ingestion-spec.html#granularityspec)) is unreasonable because information about that
|
||||
smaller granularity is not present in the indexed data. So, if the query time granularity is smaller than the ingestion
|
||||
time query granularity, Druid produces results that are equivalent to having set `granularity` to `queryGranularity`.
|
||||
|
||||
|
||||
If you change the granularity to `all`, you will get everything aggregated in 1 bucket,
|
||||
|
|
Loading…
Reference in New Issue