[
https://issues.apache.org/jira/browse/BEAM-8393?focusedWorklogId=333556&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-333556
]
ASF GitHub Bot logged work on BEAM-8393:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Oct/19 16:06
Start Date: 24/Oct/19 16:06
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #9784:
[BEAM-8393] Fix Java BigQueryIO clustering support for multiple partitions
URL: https://github.com/apache/beam/pull/9784
----------------------------------------------------------------
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: 333556)
Time Spent: 1h 10m (was: 1h)
> Java BigQueryIO clustering support breaks on multiple partitions
> ----------------------------------------------------------------
>
> Key: BEAM-8393
> URL: https://issues.apache.org/jira/browse/BEAM-8393
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.15.0, 2.16.0
> Reporter: Jeff Klukas
> Assignee: Jeff Klukas
> Priority: Critical
> Fix For: 2.17.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Support for writing to clustered tables in BigQuery was added in 2.15, which
> involved adding a new optional clustering field to TableDestination.
> Clustering support is working for most cases, but fails with errors about
> incompatible partitioning specifications for any data that is handled by the
> MultiplePartitions branch of BigQueryIO logic.
> There is a case in that code path where we provide a modified
> TableDestination and neglect to copy the clustering definition, so the final
> load job does not include any clustering columns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
