[ https://issues.apache.org/jira/browse/AIRFLOW-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaxil Naik closed AIRFLOW-559. ------------------------------ Resolution: Not A Problem We don't need this as we plan to deprecate use of *args and **kwargs and we already have `src_fmt_configs` parameter (https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/operators/bigquery_operator.py#L463) in the currently needed Bigquery operators where we might need to set extra parameters. > Add support for BigQuery kwarg parameters > ----------------------------------------- > > Key: AIRFLOW-559 > URL: https://issues.apache.org/jira/browse/AIRFLOW-559 > Project: Apache Airflow > Issue Type: Improvement > Components: contrib, gcp > Reporter: Sam McVeety > Assignee: Sam McVeety > Priority: Minor > Fix For: Airflow 1.8 > > > Many of the operators in > https://github.com/apache/incubator-airflow/tree/master/airflow/contrib/operators > add parameters over time, and plumbing these through multiple layers of > calls isn't always a high priority. > The operators (and hooks) should support an end-to-end kwargs parameter that > allows for new fields (e.g. useLegacySql, defaultDataset) to be added by > users without needing to change the underlying code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)