-
Notifications
You must be signed in to change notification settings - Fork 3.8k
update timeseries to reflect NULL filling #15512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
docs/querying/timeseriesquery.md
Outdated
| upon the grand total aggregations. | ||
|
|
||
| ## Zero-filling | ||
| ## NULL filling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should call this "Empty filling" or "Empty bucket filling" or something similar?
It doesn't actually always fill with zeros or nulls depending on the mode, rather it fills with the default values of the aggregator functions. Since they aggregate no rows, only the default value is there. https://github.com/apache/druid/blob/master/docs/querying/sql-aggregations.md has the default values of the aggregators.
docs/querying/timeseriesquery.md
Outdated
| ## NULL filling | ||
|
|
||
| Timeseries queries normally fill empty interior time buckets with zeroes. For example, if you issue a "day" granularity | ||
| By default timeseries queries fill empty interior time buckets with NULL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment about default aggregator value(s), and in other places too.
Co-authored-by: Victoria Lim <vtlim@users.noreply.github.com>
Updates timeseries docs to reflect the impact of
druid.generic.useDefaultValueForNull=falseThis PR has: