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/07/09 01:31:10 UTC
[GitHub] [incubator-druid] pdeva commented on issue #8041: Undocumented,
seemingly random choosing of inital value timestamp for SQL results
pdeva commented on issue #8041: Undocumented, seemingly random choosing of inital value timestamp for SQL results
URL: https://github.com/apache/incubator-druid/issues/8041#issuecomment-509451381
yess! i just came to the same conclusion.
we ingest at every 10 seconds, so thats why its jumping at 07:58.
However, take the query timestamp of 07:50:
Given the query 07:50 to 00:37, with granularity PT60S, i expected the rollup to be as follows:
07:50 - 08:50
08:50 -09:50,
etc.
However, druid automatically assumes the begin time to be 07:00 which is not intended, since begin time is explicitly specified at 07:50.
How does one achieve the above desired result then with druid sql?
----------------------------------------------------------------
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