[
https://issues.apache.org/jira/browse/BEAM-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiru Tang reassigned BEAM-14528:
--------------------------------
Assignee: Yiru Tang
> Data type and conversions are stricter for BQ sinks
> ---------------------------------------------------
>
> Key: BEAM-14528
> URL: https://issues.apache.org/jira/browse/BEAM-14528
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: KK Ramamoorthy
> Assignee: Yiru Tang
> Priority: P2
>
> From [https://github.com/apache/beam/pull/17404], it seems like the timestamp
> conversion has been made stricter, such that the pipeline only accepts
> timestamps in the form “2022-05-09T18:04:59Z”.
>
> Here are some formats that previously worked, but seem to no longer be
> accepted:
> “2022-05-09 18:04:59”
> “2022-05-09T18:04:59”
> “2022-05-09T18:04:59.739-07:00”
>
> Also from the same pull request, it seems to no longer accept integers in
> fields marked as floats
>
> Unexpected value :0, type: class java.lang.Integer. Table field name: a,
> type: FLOAT64
>
> Are these the desired behaviors? It’s different from the behavior I’ve
> observed when using the Streaming Inserts method.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
