[jira] [Commented] (BEAM-10340) Lost of precision when casting ZetaSQL time with microsecond-precision

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199518#comment-17199518 ] 

Beam JIRA Bot commented on BEAM-10340:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Lost of precision when casting ZetaSQL time with microsecond-precision 
> -----------------------------------------------------------------------
>
>                 Key: BEAM-10340
>                 URL: https://issues.apache.org/jira/browse/BEAM-10340
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Zijie Song
>            Assignee: Robin Qiu
>            Priority: P3
>              Labels: stale-assigned
>
> 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.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)