ashokballolli opened a new issue, #34117:
URL: https://github.com/apache/airflow/issues/34117

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### What happened
   
   Version: 2.2.3+composer
   
   The BigQueryInsertJobOperator from 
airflow.providers.google.cloud.operators.bigquery takes the query to execute as 
part of the parameter configuration.
   When it completed the execution of the task, I am not able to see the query 
its executed in the log like any other operator.
   
   ```
   insert_query_job = BigQueryInsertJobOperator(
       task_id="insert_query_job",
       configuration={
           "query": {
               "query": INSERT_ROWS_QUERY,
               "useLegacySql": False,
               "priority": "BATCH",
           }
       },
       location=location,
   )
   ```
   
   This task doesn't print the INSERT_ROWS_QUERY in the logs
   
   ### What you think should happen instead
   
   It would be great for debugging if this operator prints the query its 
executed replacing the JINJA variables.
   
   ### How to reproduce
   
   Run the task with query to insert the data into BigQuery table and check the 
logs from the logs tab on Airflow UI
   
   
   ### Operating System
   
   Google Cloud Composer
   
   ### Versions of Apache Airflow Providers
   
   2.2.3+composer
   But I guess this is valid for all the versions of Airflow
   
   ### Deployment
   
   Google Cloud Composer
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to