You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Matthew Ouyang (Jira)" <ji...@apache.org> on 2021/04/07 13:43:00 UTC
[jira] [Updated] (BEAM-12059) BigQueryUtils doesn't process
DATETIME field that includes a T
[ https://issues.apache.org/jira/browse/BEAM-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Ouyang updated BEAM-12059:
----------------------------------
Resolution: Fixed
Status: Resolved (was: In Progress)
> BigQueryUtils doesn't process DATETIME field that includes a T
> --------------------------------------------------------------
>
> Key: BEAM-12059
> URL: https://issues.apache.org/jira/browse/BEAM-12059
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.28.0
> Reporter: Matthew Ouyang
> Assignee: Matthew Ouyang
> Priority: P2
> Fix For: 2.30.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> A query with a DATETIME always returns a string with a literal T between the date and the time. The BIGQUERY_DATETIME_FORMATTER doesn't account for the literal T and won't be able
> Steps to reproduce
> # BigQueryIO.readTableRowsWithSchema
> # Query with a DATETIME function or field. Functions will always output a literal T (https://cloud.google.com/bigquery/docs/reference/standard-sql/datetime_functions). I can't find the supporting documentation for fields though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)