This is an automated email from the ASF dual-hosted git repository. damccorm pushed a commit to branch users/damccorm/bqDocString in repository https://gitbox.apache.org/repos/asf/beam.git
commit 345ae28dd9df1f92c6363a11c91fc1bf94fc37e7 Author: Danny McCormick <[email protected]> AuthorDate: Wed Jan 29 11:50:06 2025 -0500 Fix bq write doc string I was confused why this wasn't rendering correctly in https://beam.apache.org/releases/yamldoc/current/#writetobigquery - I think this is why --- sdks/python/apache_beam/yaml/yaml_io.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sdks/python/apache_beam/yaml/yaml_io.py b/sdks/python/apache_beam/yaml/yaml_io.py index 9392cd6aee5..95d06bd07f0 100644 --- a/sdks/python/apache_beam/yaml/yaml_io.py +++ b/sdks/python/apache_beam/yaml/yaml_io.py @@ -147,7 +147,7 @@ def write_to_bigquery( Defaults to `{BigQueryDisposition.CREATE_IF_NEEDED}`. - write_disposition (BigQueryDisposition): A string describing what happens + write_disposition (BigQueryDisposition): A string describing what happens if the table has already some data. Possible values are: * :attr:`{BigQueryDisposition.WRITE_TRUNCATE}`: delete existing rows. @@ -159,7 +159,7 @@ def write_to_bigquery( Defaults to `{BigQueryDisposition.WRITE_APPEND}`. - error_handling: If specified, should be a mapping giving an output into + error_handling: If specified, should be a mapping giving an output into which to emit records that failed to bet written to BigQuery, as described at https://beam.apache.org/documentation/sdks/yaml-errors/ Otherwise permanently failing records will cause pipeline failure.
