LuciferYang commented on PR #42039:
URL: https://github.com/apache/spark/pull/42039#issuecomment-1648096547

   For this case, the original value is nanosecond precision: V1, which is 
result of encoded+decoded is microsecond precision:V2, so V1 cannot be equal to 
V2.
   
   Alternatively, we should change Spark to maintain nanosecond accuracy for 
all scenarios, but I am not sure if this will cause a break change for the 
current versio. If it's a break change, I'm not sure if it should be done in 
Spark 3.5 or if 4.0 is more suitable.
   
   
   
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to