AymaneElmahi opened a new issue, #59344: URL: https://github.com/apache/airflow/issues/59344
### Description `BigQueryToGCSOperator` currently returns `None` from `execute()`, so no XCom is produced. This makes it difficult for downstream tasks to know where BigQuery exported the data. I propose that the operator returns the value of `destination_cloud_storage_uris` from `execute()` (and from `execute_complete()` when deferrable mode is used). This change is: - backward-compatible (the operator previously returned `None`) - consistent with Airflow’s design where operators return their outputs via XCom - aligned with other transfer operators that expose output paths - helpful for downstream consumers of exported data If maintainers agree, I am happy to submit a PR implementing this. ### Use case/motivation Many BigQuery export workflows need to consume the exported files in downstream Airflow tasks (e.g., loading into GCS, Firestore, BigQuery Load jobs, or custom processing). However, `BigQueryToGCSOperator` currently returns `None`, so no XCom is available to downstream tasks. Returning the destination URI list would: - make DAGs easier to author and understand - avoid redundant GCS listing operations - provide consistency with other operators that expose their outputs - improve interoperability between BigQuery → GCS → next-step workflows - enable dynamic downstream tasks that depend on the export result This is especially useful for templated URIs or partitioned tables where downstream tasks must know the exact location of exported files. ### 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]
