You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/13 23:52:00 UTC

[jira] [Commented] (BEAM-12994) Python SDK BigQuery `schemaUpdateOptions`

    [ https://issues.apache.org/jira/browse/BEAM-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475861#comment-17475861 ] 

Kenneth Knowles commented on BEAM-12994:
----------------------------------------

Seems like a nice change. Needs to be made in a backwards compatible way. Would you be interested in giving it a try?

> Python SDK BigQuery `schemaUpdateOptions`
> -----------------------------------------
>
>                 Key: BEAM-12994
>                 URL: https://issues.apache.org/jira/browse/BEAM-12994
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-py-gcp
>    Affects Versions: 2.33.0
>            Reporter: Judah
>            Priority: P3
>
> I noticed that in the Java SDK `schemaUpdateOptions` are exposed clearly to the user: [https://beam.apache.org/releases/javadoc/2.32.0/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.Write.html]
>  
> Whereas, in the Python SDK this option seems to only be able to be passed through `additional_bq_paramaters`. 
>  
> Is this something which should be resolved? Perhaps add the `schemaUpdateOptions` to [https://github.com/apache/beam/blob/b9457b711029051a837255e1bb516e55d32e56d5/sdks/python/apache_beam/io/gcp/bigquery.py#L437] and expose a `kwarg` to pass them in? 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)