ahmedabu98 commented on PR #39804:
URL: https://github.com/apache/beam/pull/39804#issuecomment-5330431667

   This type may not be a straightforward redo of the Date type, since 
conceptually it can be described by different precisions. Using nanosecond 
precision makes sense today, but one could argue it's arbitrary, and future 
applications may require a higher precision. 
   
   Check out the timestamp logical type ([design 
doc](https://s.apache.org/beam-timestamp-strategy) + [Java 
implementation](https://github.com/apache/beam/pull/36705) + [Python 
implementation](https://github.com/apache/beam/pull/39537)), where we include a 
"precision" parameter. I think it makes sense to do something similar here.
   
   Python already has a custom Timestamp type. I think we can do with a new 
custom Time type that behaves similarly, but others may have opinions.
   
   I think at the very least, this topic deserves a discussion in the mailing 
dev list. Feel free to send a message there so others can pitch in 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to