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

Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2019/08/27 09:00:00 UTC

[jira] [Updated] (BEAM-8047) Handle overflow when converting from millis to micros

     [ https://issues.apache.org/jira/browse/BEAM-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-8047:
-------------------------------
    Description: 
When converting from Joda Instant/Datetime, what can be gotten is epoch millis, but conversions require epoch micros, so * 1000L is applied, but it definitely has overflow issue and need to be handle appropriately.

This issue exists in zetasql planner.

  was:
When converting from Joda Instant/Datetime, what can be gotten is epoch millis, but conversions require epoch macros, so * 1000L is applied, but it definitely has overflow issue and need to be handle appropriately.

This issue exists in zetasql planner.


> Handle overflow when converting from millis to micros
> -----------------------------------------------------
>
>                 Key: BEAM-8047
>                 URL: https://issues.apache.org/jira/browse/BEAM-8047
>             Project: Beam
>          Issue Type: Sub-task
>          Components: dsl-sql-zetasql
>            Reporter: Rui Wang
>            Priority: Major
>
> When converting from Joda Instant/Datetime, what can be gotten is epoch millis, but conversions require epoch micros, so * 1000L is applied, but it definitely has overflow issue and need to be handle appropriately.
> This issue exists in zetasql planner.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)