You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/23 18:37:00 UTC

[jira] [Commented] (AIRFLOW-5542) Export a BigQuery query result to GCS

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

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

meftasadat commented on pull request #6173: [AIRFLOW-5542] Added BQ query results export to GCS  operator
URL: https://github.com/apache/airflow/pull/6173
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following AIRFLOW-5542 (https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. 
     - https://issues.apache.org/jira/browse/AIRFLOW-5522
   
   ### Description
   
   - Executes a BigQuery Standard SQL query and exports query results to GCS.
   
   ### 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.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


> Export a BigQuery query result to GCS
> -------------------------------------
>
>                 Key: AIRFLOW-5542
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5542
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: operators
>    Affects Versions: 1.10.5
>            Reporter: Mefta Sadat
>            Priority: Minor
>
> h2. Problem
> There is currently no direct operator to export a BQ query result dataset to GCS.
> h2. Proposed implementation
> This problem can be solved by creating a temporary table, storing the query results in the temp table, exporting the table to GCS and then finally deleting the table
> The following methods in airflow.gcp.hooks.bigquery_hook can be leveraged to achieve this solution:
> create_empty_dataset -> run_query -> run_extract -> run_table_delete -> delete_dataset
> The proposer operator is just a wrapper around these methods. It executes the above-mentioned methods in the necessary order and handles any exceptions that may occur.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)