You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/03/03 20:02:42 UTC
[GitHub] [spark] srowen commented on issue #23945: [SPARK-27035][SQL] Get
more precise current time
srowen commented on issue #23945: [SPARK-27035][SQL] Get more precise current time
URL: https://github.com/apache/spark/pull/23945#issuecomment-469058368
This seems reasonable. I'm trying to imagine a case where it would cause problems. I suppose if you were saving this timestamp and later comparing it exactly to a timestamp without actual microsecond precision, they'd stop matching. Worth a release note I think, but an OK change for Spark 3, if it's going to be a pretty rare case. Am I missing other reasons this change could be surprising or affect a lot of code?
----------------------------------------------------------------
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: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org