[GitHub] [druid] FrankChen021 commented on issue #9991: Loss of sub-second time info when parsing posix-formatted time field

[GitBox <gi...@apache.org>]

FrankChen021 commented on issue #9991:
URL: https://github.com/apache/druid/issues/9991#issuecomment-639989256


   posix timestamp is a value of SECONDS since epoch. Druid takes the input as type of LONG, so the fraction is ignored. To keep the subsecond, you could turn the value into format of MILLISCONDS timestamp, that is 1591349534205 in your example. 
   
   In practice, query granularity is widely used to  utilize the roll-up functionality, which means there's no need to care about the exact timestamp of every record. Because of loss of subsecond, it's equivalent to set the query granularity to SECOND. So I think the loss is acceptable.


----------------------------------------------------------------
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



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