[
https://issues.apache.org/jira/browse/BEAM-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958069#comment-16958069
]
Kenneth Knowles commented on BEAM-8393:
---------------------------------------
The wording of Jira's priorities is unfortunate. By setting Fix Version it is
already declared to be a release blocker, regardless of priority. I just think
of them as P0-P4, where P0 means someone should probably get paged (like if all
tests are failing, blocking the community).
> 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: Blocker
> Fix For: 2.17.0
>
> Time Spent: 1h
> 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)
