Fix GCSSynchronizeBucketsOperator timeout error #37237
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes: #27488.
It solves the timeout error when trying to synchronize large files by using the
rewritefunction instead ofcopy.There was also previously a bug when synchronizing from a subdirectory where an empty subdirectory gets created which is solved by this PR.
For e.g synchronizing files in subdirectory
bigdata2from source bucket would unnecessarily create an emptybigdata2folder as seen in the image. This should not happen if I understand the docs correctly.The behaviour of GCSSynchronizeBucketsOperator otherwise remains the same.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.