RustedBones opened a new pull request, #33163: URL: https://github.com/apache/beam/pull/33163
when writing to BQ with avro, if the table schema contains `DATE`, `TIME`, `TIMESTAMP` columns, the default schema factory should create avro fields with matching logical type. There is still an issue with `DATETIME`: `BigQueryAvroUtils::toGenericAvroSchema` favored generating schema for the reading side and generates an avro filed with `string(datetime)` type. This can't be used on write (expecting `long(local-timestamp-millis)` or `long(local-timestamp-micros)`). See note in [doc](https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-avro#logical_types) > When exporting to Avro from BigQuery, DATETIME is exported as a STRING with a custom logical time that is not recognized as a DATETIME upon importing back into BigQuery. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
