[jira] [Commented] (AIRFLOW-1874) Support standard SQL in Check, ValueCheck and IntervalCheck BigQuery operators

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on AIRFLOW-1874:
-----------------------------------------

xnuinside opened a new pull request #3717: [AIRFLOW-1874] use_legacy_sql added to BigQueryCheck operators
URL: https://github.com/apache/incubator-airflow/pull/3717
 
 
   Hi everyone! I saw the old task relative to my current work scope and decide to do this little PR ) 
   Just adding use_legacy_sql to BigQueryCheck operator.
   
   [AIRFLOW-1874] use_legacy_sql added to BigQueryCheck operators
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
   
   ### Code Quality
   
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Support standard SQL in Check, ValueCheck and IntervalCheck BigQuery operators
> ------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-1874
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1874
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: contrib, gcp, operators
>            Reporter: Guillermo Rodríguez Cano
>            Assignee: Iuliia Volkova
>            Priority: Major
>             Fix For: 2.0.0
>
>
> BigQueryCheckOperator, BigQueryValueCheckOperator and BigQueryIntervalCheckOperator do not support disabling use of default legacy SQL in BigQuery.
> This is a major blocker to support correct migration to standard SQL when queries are complicated. For example, a query that can be queried in legacy SQL may be blocked from any subsequent view done in standard SQL that this view uses as the queries are bound to either standard or legacy SQL but not a mix.
> These operators inherit from base ones of the same name (without the BigQuery prefix) from Airflow which may make the process more complicated as the flag to use standard SQL should be enabled because the underlying BigQueryHook has the corresponding parameter, use_legacy_sql, set to True, when running a query. But it is not possible to pass parameters all the way to it via the aforementioned operators.
> The workaround of including #standardSQL and a new line before the query doesn't work either as there is mismatch. BigQuery reports the following in fact: "Query text specifies use_legacy_sql:false, while API options specify:true"
> A workaround for queries on views using standard SQL is to persist the result of the query in a temporary table, then run the check operation and thereafter delete the temporary table. 



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