You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "limhwanhee (via GitHub)" <gi...@apache.org> on 2024/01/23 06:11:12 UTC

[I] order by __time and TIME_PARSE bug. (druid)

limhwanhee opened a new issue, #15740:
URL: https://github.com/apache/druid/issues/15740

   Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").
   
   ### Affected Version
   
   24.0.0
   
   ### Description
   
   I have a Table like the one below.
   
   |__time |test1|test2|start_time|value|
   |---|---|---|---|----|
   |2024-01-23T00:00:00.000Z|A|C|2024/01/23 00:00:00|1|
   |2024-01-23T00:00:00.100Z|A|C|2024/01/23 00:00:00|2|
   |2024-01-23T00:00:00.200Z|B|C|2024/01/23 00:00:00|3|
   |...|...|...|...|...|
   |2024-01-23T00:01:00.000Z|A|C|2024/01/23 00:00:00|1|
   |2024-01-23T00:01:00.100Z|A|C|2024/01/23 00:00:00|2|
   |2024-01-23T00:01:00.200Z|B|C|2024/01/23 00:00:00|3|
   |...|...|...|...|...|
   
   Write the query statement as follows.
   
   ```
   select * from (SELECT __time, test1, test2, TIME_PARSE("start_time", 'yyyy/MM/dd HH:mm:ss') as "stime", value from test_table order by __time)
   where "stime" >= TIMESTAMP '2024-01-24 00:00:00'
   order by __time
   ```
   
   The correct answer I expect is
   
   |__time |test1|test2|stime|value|
   |---|---|---|---|----|
   |2024-01-24T00:00:00.000Z|C|A|2024-01-24T00:00:00Z|1|
   |2024-01-24T00:00:00.100Z|C|A|2024-01-24T00:00:00Z|2|
   |2024-01-24T00:00:00.200Z|C|A|2024-01-24T00:00:00Z|3|
   |...|...|...|...|...|
   |2024-01-24T00:01:00.000Z|F|X|2024-01-24T00:00:00Z|1|
   |2024-01-24T00:01:00.100Z|F|X|2024-01-24T00:00:00Z|2|
   |2024-01-24T00:01:00.200Z|F|X|2024-01-24T00:00:00Z|3|
   |...|...|...|...|...|
   
   
   However, the result is shown below.
   
   |__time |test1|test2|stime|value|
   |---|---|---|---|----|
   |2024-01-24T00:00:00.000Z|C|A|2024-01-24T23:56:xxZ|1|
   |2024-01-24T00:00:00.100Z|C|A|2024-01-24T23:xx:xxZ|2|
   |2024-01-24T00:00:00.200Z|C|A|2024-01-24T23:59:xxZ|3|
   |...|...|...|...|...|
   |2024-01-24T00:01:00.000Z|F|X|2024-01-24T23:xx:xxZ|1|
   |2024-01-24T00:01:00.100Z|F|X|2024-01-24T23:xx:xxZ|2|
   |2024-01-24T00:01:00.200Z|F|X|2024-01-24T23:xx:xxZ|3|
   |...|...|...|...|...|
   
   The original table has a normal start_time.
   What could be the cause?


-- 
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: commits-unsubscribe@druid.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] order by __time and TIME_PARSE bug. (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #15740: order by __time and TIME_PARSE bug.
URL: https://github.com/apache/druid/issues/15740


-- 
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: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] order by __time and TIME_PARSE bug. (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #15740:
URL: https://github.com/apache/druid/issues/15740#issuecomment-2502329829

   This issue has been closed due to lack of activity. If you think that
   is incorrect, or the issue requires additional review, you can revive the issue at
   any time.


-- 
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: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] order by __time and TIME_PARSE bug. (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #15740:
URL: https://github.com/apache/druid/issues/15740#issuecomment-2445557648

   This issue has been marked as stale due to 280 days of inactivity.
   It will be closed in 4 weeks if no further activity occurs. If this issue is still
   relevant, please simply write any comment. Even if closed, you can still revive the
   issue at any time or discuss it on the dev@druid.apache.org list.
   Thank you for your contributions.


-- 
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: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org