techdocsmith commented on a change in pull request #11672:
URL: https://github.com/apache/druid/pull/11672#discussion_r705510883
##########
File path: docs/querying/granularities.md
##########
@@ -28,9 +28,11 @@ sidebar_label: "Granularities"
> language. For information about time functions available in SQL, refer to the
> [SQL documentation](sql.md#time-functions).
-The granularity field determines how data gets bucketed across the time
dimension, or how it gets aggregated by hour, day, minute, etc.
+The granularity determines how data gets bucketed across the time dimension,
or how it gets aggregated by hour, day, minute, etc.
Review comment:
```suggestion
Granularity determines how to bucket data across the time dimension, or how
to aggregate data by hour, day, minute, etc.
```
##########
File path: docs/querying/granularities.md
##########
@@ -28,9 +28,11 @@ sidebar_label: "Granularities"
> language. For information about time functions available in SQL, refer to the
> [SQL documentation](sql.md#time-functions).
-The granularity field determines how data gets bucketed across the time
dimension, or how it gets aggregated by hour, day, minute, etc.
+The granularity determines how data gets bucketed across the time dimension,
or how it gets aggregated by hour, day, minute, etc.
-It can be specified either as a string for simple granularities or as an
object for arbitrary granularities.
+For example, use time granularities in [native queries](querying.md) to bucket
results by time, and in the `dataSchema` \\
[`granularitySpec`](../ingestion/ingestion-spec.md#granularityspec) section of
ingestion specifications to segment incoming data.
Review comment:
This topic is under "Querying". Wondering if the outbound link to
Granularity spec is necessary. For example I would think it would be more
likely for someone to come here from there than the other way round.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
