petermarshallio commented on a change in pull request #11672:
URL: https://github.com/apache/druid/pull/11672#discussion_r705980811
##########
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:
Hey @techdocsmith yet again you are critiquing my work. What is this.
I am most upset.
Not really 🤗
So this is my experience? Which may explain my logic? here? about this?
proposal?
Granularities, yes, are under Querying. And yet, forsooth, I have never
used them for queries (forsooth, I do use SQL mostly). The only time I
personally? have? accessed this page? is when I wanted to refer? to other ways
of setting the queryGranularity and knowing what's possible? – especially when
different timezones need to be accounted for?
Thusly, I felt it would be appropriate that, if someone were to land on this
"common concept" page, it ought to point not just to how they're used in
queries, but other places they are used, namely, that most important of usage,
within, thus, and forsooth, the `dataSchema`, and so on, and so forth.
🙇🏻
--
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]
