[
https://issues.apache.org/jira/browse/BEAM-9321?focusedWorklogId=396275&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-396275
]
ASF GitHub Bot logged work on BEAM-9321:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Mar/20 18:17
Start Date: 02/Mar/20 18:17
Worklog Time Spent: 10m
Work Description: pabloem commented on issue #10869: [BEAM-9321] Add
BigQuery Avro logical type support on write
URL: https://github.com/apache/beam/pull/10869#issuecomment-593542523
I agree with Alex on this - I think we should just always handle the logical
type. I have two questions:
- Would it be backwards incompatible if we forced always handling the
logical types? I think we should just make it the default.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 396275)
Time Spent: 1h 10m (was: 1h)
> BigQuery avro write logical type support
> ----------------------------------------
>
> Key: BEAM-9321
> URL: https://issues.apache.org/jira/browse/BEAM-9321
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.19.0
> Reporter: Filipe Regadas
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> With 2.18.0 we are able to write GenericRecords to BigQuery. However, writing
> does not respect Avro <-> BigQuery data type conversion
> ([docs|https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-avro#logical_types])
> we need to set the useAvroLogicalTypes option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
