TY-chang opened a new issue, #24578: URL: https://github.com/apache/airflow/issues/24578
### Description - I met LoadJob bug in `BigQueryInsertJobOperator` and tried to use `GCSToBigQueryOperator` instead when update from Airflow 2.2.5 to 2.3.2. ### Use case/motivation - most BigQuery-related operator recommend that we should use `insert_job()`, but gcs_to_bq_operator still use `run_load ()`. - `GCSToBigQueryOperator` still uses lots of parameter to build config. Not like `BigQueryInsertJobOperator` which uses a clean configuration. The configuration is much straightforward and easy to follow. - I would like to know whether to keep `GCSToBigQueryOperator` and replace `run_load` with `insert_job`, Or have `BigQueryInsertJobOperator`. If we could replace `run_load` with `insert_job` in `GCSToBigQueryOperator` , all BigQuery-related operator could be more consistent. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] 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]
