[
https://issues.apache.org/jira/browse/BEAM-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547209#comment-17547209
]
Kenneth Knowles commented on BEAM-4789:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18977
> BigQueryIO WRITE_TRUNCATE documentation is out of date
> ------------------------------------------------------
>
> Key: BEAM-4789
> URL: https://issues.apache.org/jira/browse/BEAM-4789
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp, sdk-py-core
> Reporter: Ahmet Altay
> Priority: P3
>
> Apache Beam 2.5 documentation
> ([https://beam.apache.org/documentation/sdks/javadoc/2.5.0/]), states that
>
> "WRITE_TRUNCATE
> public static final BigQueryIO.Write.WriteDisposition WRITE_TRUNCATE
> Specifies that write should replace a table.
> The replacement *may occur in multiple steps* - for instance by first
> removing the existing table, then creating a replacement, then filling it in.
> *This is not an atomic operation*, and external programs may see the table in
> any of these intermediate steps."
>
> However WRITE_TRUNCATE is an atomic BigQuery operation. The documentation
> needs to be updated.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
