airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-1267) BigQueryCheckOperator is not configurable on the use_legacy_sql flag
Date Mon, 22 Jan 2018 17:28:00 GMT

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

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

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

[AIRFLOW-1267][AIRFLOW-1874] Add dialect parameter to BigQueryHook

Allows a default BigQuery dialect to be specified
at the hook level, which is threaded through to
the
underlying cursors.

This allows standard SQL dialect to be used,
while maintaining compatibility with the
`DbApiHook` interface.

Addresses AIRFLOW-1267 and AIRFLOW-1874

Closes #2964 from ji-han/master


> BigQueryCheckOperator is not configurable on the use_legacy_sql flag
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-1267
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1267
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: configuration, contrib, db
>            Reporter: Lan Xu
>            Priority: Critical
>
> The BigqueryCheckOperator is not configurable to use standard sql, which is causing our
DAGs to fail. It might be due to the BigQuery hook configs using legacy sql as default, and
the check operator class never has access to change that configuration. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message