From 10d6b0318d0546a170d8b33c26f6565ef3343ea7 Mon Sep 17 00:00:00 2001 From: Clint Wylie Date: Thu, 27 Jun 2019 08:51:22 -0700 Subject: [PATCH] clarify granularity docs (#7977) --- docs/content/querying/granularities.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/content/querying/granularities.md b/docs/content/querying/granularities.md index 7dc02ef4ef9..4953ead0c6f 100644 --- a/docs/content/querying/granularities.md +++ b/docs/content/querying/granularities.md @@ -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,