You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/04/05 16:15:41 UTC

[jira] [Commented] (BEAM-1716) Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery

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

Daniel Halperin commented on BEAM-1716:
---------------------------------------

Would you like to send a PR with a test showing an issue and a fix?

> Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery
> ----------------------------------------------------------------------------------------------
>
>                 Key: BEAM-1716
>                 URL: https://issues.apache.org/jira/browse/BEAM-1716
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>    Affects Versions: 0.5.0
>            Reporter: Tobias Feldhaus
>              Labels: newbie, starter
>             Fix For: First stable release
>
>
> When using an Instant type in a TableRow, and a TIMESTAMP field in the TableFieldSchema, one has to convert the Instant via 
> instant.getMillis() / 1000
> to match the BigQuery TIMESTAMP that is "A positive or negative decimal number. A positive number specifies the number of seconds since the epoch".
> In the Dataflow 1.9 SDK this conversion is done automatically.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)