[jira] [Commented] (AIRFLOW-638) Added schema_update_options to BigQueryBaseCursor and GoogleCloudStorageToBigQueryOperator

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AIRFLOW-638:
---------------------------------------------------------

Commit beb285205780d230f6862fad56e609bb81996c01 in incubator-airflow's branch refs/heads/master from [~Jalepeno112]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=beb2852 ]

[AIRFLOW-638] Add schema_update_options to GCP ops

Closes #1891 from
Jalepeno112/feature/gcs_to_bq_schemaUpdateOptions


> Added schema_update_options to BigQueryBaseCursor and GoogleCloudStorageToBigQueryOperator
> ------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-638
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-638
>             Project: Apache Airflow
>          Issue Type: New Feature
>            Reporter: Giovanni Briggs
>            Assignee: Giovanni Briggs
>            Priority: Minor
>
> Was trying to upload data to a BigQuery table along with a change in my schema.  The way that the GoogleCloudStorageToBigQueryOperator currently works, this is not possible, but BigQuery does support changing a table's schema as a side-effect of a load operation via the "schemaUpdateOptions" field: https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs#configuration.load.schemaUpdateOptions
> Added schema_update_options as a parameter to both the GoogleCloudStorageToBigQueryOperator and consequently the BigQueryBaseCursor to enable use of the schemaUpdateOptions field during load operations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)