beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Feldhaus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1716) Using Instant type in TableRow should map to the right output format for TIMESTAMP in BigQuery
Date Tue, 25 Apr 2017 15:24:06 GMT

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

Tobias Feldhaus commented on BEAM-1716:
---------------------------------------

PEBCAK -  Problem Exists Between Chair And Keyboard

...calling {{.toString()}} on an Instant works like before, since BigQuery accepts  ISO-8601
formats (RFC-3339) and {{toString()}} on Joda instants uses ISO 8601 too. 
The behavior of Beam and Dataflow is absolutely identical - one has either to call {{toString()}}
or do the  {{getMillis() / 1000}} calculation with Instant datatypes.

> 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)

Mime
View raw message