You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/03/21 22:10:42 UTC
[GitHub] [incubator-druid] gianm commented on issue #7132: [DISCUSS]
Behavior of Granularity.getIterable()
gianm commented on issue #7132: [DISCUSS] Behavior of Granularity.getIterable()
URL: https://github.com/apache/incubator-druid/issues/7132#issuecomment-475422462
> The query result may contain timestamps of not specified in the query spec which can mislead users.
At query time, I don't think this happens, because elsewhere in the query processing stack data is clipped to the actual input interval. IIRC, what these intervals are used for is populating stuff like the "timestamp" of a time-granular result. If you think about the semantics of this method as returning all granular buckets that overlap the input interval, then from that perspective it makes sense to _not_ clip to the input interval.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org