[
https://issues.apache.org/jira/browse/BEAM-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123164#comment-17123164
]
Beam JIRA Bot commented on BEAM-5216:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> BigQueryIO multi-partitioned write doesn't work for streaming writes
> --------------------------------------------------------------------
>
> Key: BEAM-5216
> URL: https://issues.apache.org/jira/browse/BEAM-5216
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P2
> Labels: stale-P2
>
> BigQueryIO performes multi-partitioned write (MultiPartitionsWriteTables
> step) when there's more data than the quota allowed by BigQuery (10k files or
> 11TB of data) to be written to a single BQ table.
>
> When writing using load jobs in streaming mode (with a triggering frequency)
> we hit following location where we set CREATE_DISPOSITION to CREATE_NEVER for
> all panes other than the first one. This is fine when we are writing a single
> partition (all panes of a window should write to the same table) but when
> there are multiple partitions this is incorrect since we need to create temp
> tables for all panes.
> [https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteTables.java#L165]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
