You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 17:08:48 UTC

[GitHub] [beam] damccorm opened a new issue, #20351: Lost of precision when casting ZetaSQL time with microsecond-precision

damccorm opened a new issue, #20351:
URL: https://github.com/apache/beam/issues/20351

   When we cast ZetaSQL time value with microsecond-precision to string, it currently would cause lost of precision.
   
   For example, when we parse the following SQL statement:
    
   "SELECT CAST(s1 as TIME) as t2, CAST(t1 as STRING) as s2
   
   FROM (SELECT '12:34:56.123456' as s1, TIME '12:34:56.123456' as t1)"
   
   the result would be 12:34:46, and the corresponding microsecond precision would lost.
   
    
   
   Imported from Jira [BEAM-10340](https://issues.apache.org/jira/browse/BEAM-10340). Original Jira may contain additional context.
   Reported by: zijiesong.


-- 
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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org