This message was deleted.

Hi Ryan, thanks for pointing that out ... I have notified the doc team to take a look. Fyi useDefaultValueForNull should be

false

by default, meaning disabled, not enabled?

yea the flag requires some mental gymnastics. it now defaults to false like you said, so Druid no longer uses the type's default value when the value is null and instead just uses null

Internal discussion suggests that what you are seeing is the result of the aggregate functions that are employed as part of the time series function. With the new NULL handling default many aggregate functions will return a null if only nulls have been passed in. I believe a doc change is coming to explain this.