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 2022/12/06 11:37:27 UTC
[GitHub] [druid] jeclarke opened a new issue, #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
jeclarke opened a new issue, #13509:
URL: https://github.com/apache/druid/issues/13509
When calling MILLIS_TO_TIMESTAMP any milliseconds do not appear in the produced timestamp. The produced timestamp always has .000 for milliseconds.
### Affected Version
0.23.0
### Description
To reproduce this issue run the following SQL:
````
SELECT MILLIS_TO_TIMESTAMP(1670325506528) AS my_timestamp
````
The output is:
````
my_timestamp
2022-12-06T11:18:26.000Z
````
I expected the output to be:
````
my_timestamp
2022-12-06T11:18:26.528Z
````
--
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
[GitHub] [druid] k-haley1 commented on issue #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
Posted by "k-haley1 (via GitHub)" <gi...@apache.org>.
k-haley1 commented on issue #13509:
URL: https://github.com/apache/druid/issues/13509#issuecomment-1408859728
@abhishekagarwal87 are there plans to fix this bug?
--
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
[GitHub] [druid] abhishekagarwal87 commented on issue #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
Posted by "abhishekagarwal87 (via GitHub)" <gi...@apache.org>.
abhishekagarwal87 commented on issue #13509:
URL: https://github.com/apache/druid/issues/13509#issuecomment-1410260601
Thank you @LakshSingla for verifying.
--
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] MILLIS_TO_TIMESTAMP function discards the millisecond part (druid)
Posted by "sergei3000 (via GitHub)" <gi...@apache.org>.
sergei3000 commented on issue #13509:
URL: https://github.com/apache/druid/issues/13509#issuecomment-1790638274
Turns out it was a bug and it was fixed. I installed version `27.0.0` locally and `TIME_PARSE` returns milliseconds now and filtering seems to account for milliseconds as well.
--
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
[GitHub] [druid] abhishekagarwal87 closed issue #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
Posted by "abhishekagarwal87 (via GitHub)" <gi...@apache.org>.
abhishekagarwal87 closed issue #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
URL: https://github.com/apache/druid/issues/13509
--
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
[GitHub] [druid] LakshSingla commented on issue #13509: MILLIS_TO_TIMESTAMP function discards the millisecond part
Posted by "LakshSingla (via GitHub)" <gi...@apache.org>.
LakshSingla commented on issue #13509:
URL: https://github.com/apache/druid/issues/13509#issuecomment-1408970211
I tested this out on the latest master, and it is producing the expected result. I am on the latest master branch. Can you please check if upgrading to the newest version 25.0.0 resolves this bug?
<img width="1241" alt="Screenshot 2023-01-30 at 10 15 08 PM" src="https://user-images.githubusercontent.com/30999375/215540329-771f6bb7-74e5-462c-92af-f56ce27ae5e8.png">
--
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] MILLIS_TO_TIMESTAMP function discards the millisecond part (druid)
Posted by "sergei3000 (via GitHub)" <gi...@apache.org>.
sergei3000 commented on issue #13509:
URL: https://github.com/apache/druid/issues/13509#issuecomment-1790550267
Sorry about writing in this closed thread.
Did this also fix the problem that I can see in my Druid instance when `SELECT TIME_PARSE('2023-10-19T09:29:58.613Z')` results in `2023-10-19T09:29:58.000Z` cutting off the milliseconds part (I run this in Druid's web UI)? I expect the result to be `2023-10-19T09:29:58.613` keeping the milliseconds and not cutting them off.
Also filtering like `WHERE __time >= '2023-10-19T09:29:58.613Z'` returns records with timestamps above `09:29:58.000` but below `09:29:58.613` for me which seems to be related to the `TIME_PARSE` problem.
--
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