You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/10/22 17:10:01 UTC
[jira] [Updated] (BEAM-10340) Lost of precision when casting
ZetaSQL time with microsecond-precision
[ https://issues.apache.org/jira/browse/BEAM-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-10340:
---------------------------------
Labels: stale-assigned (was: )
> 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)