You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Iuliia Volkova (JIRA)" <ji...@apache.org> on 2018/08/10 11:22:00 UTC
[jira] [Commented] (AIRFLOW-559) Add support for BigQuery kwarg
parameters
[ https://issues.apache.org/jira/browse/AIRFLOW-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576123#comment-16576123 ]
Iuliia Volkova commented on AIRFLOW-559:
----------------------------------------
[~kaxilnaik] , can you close this task to avoid confusion because as you mentioned in https://github.com/apache/incubator-airflow/pull/3717 "As far as I know, there is a plan to deprecate args and kwargs keywords in Airflow."?
Because of this task about the opposite thing.
And some PRs was closed without merge based on this, for example:
[https://github.com/apache/incubator-airflow/pull/1784]
> 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)