[
https://issues.apache.org/jira/browse/BEAM-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549234#comment-17549234
]
Danny McCormick commented on BEAM-12002:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/20841
> BigQuery source creates new dataset IDs during split
> ----------------------------------------------------
>
> Key: BEAM-12002
> URL: https://issues.apache.org/jira/browse/BEAM-12002
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp, io-py-gcp
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P3
>
> If unspecified by user, source creates the temp dataset ID here:
> [https://github.com/apache/beam/blob/release-2.27.0/sdks/python/apache_beam/io/gcp/bigquery.py#L786]
> This means that re-runs of same source split workitem will have different
> temporary dataset IDs.
> If some split() calls fail before cleaning up the dataset, such datasets will
> not be cleaned up even if the job is successful (after workitem retries).
> Instead of doing this, we should create a temp dataset ID at source creation
> so that it is shared between re-runs of the same workitem. This might be
> incompatible with templates so we might have to wait till we have a SDF-based
> BigQuery source.
>
> (Java potentially have a similar bug in BigQuerySource but we have a
> withTemplateCompatability() option for Java which runs BigQuery using DoFns
> which should perform the cleanup correctly)
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
