Add flag apply_gcs_prefix to S3ToGCSOperator #31127
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
area:system-tests
provider:google
moiseenkov
force-pushed
the
s3_to_gcs_apply_gcs_prefix
branch
3 times, most recently
from
1425a32 to
5a6bd82
Compare
moiseenkov
force-pushed
the
s3_to_gcs_apply_gcs_prefix
branch
from
5a6bd82 to
20e4141
Compare
potiuk
approved these changes
May 13, 2023
80 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added parameter
apply_gcs_prefix=False.If it is set
True, then objects will be copied from S3 to GCS without copying their full source path. Instead, a new destination path will be constructed as a source path, where S3 prefix is replaced by a GCS prefix. It allows users to copy files from S3 into a specific folder in GCS.The default value is
apply_gcs_prefix=Falsewhich refers to the old operators behavior, therefore merging this PR won't affect existing users, unless they change the value for this parameter in their DAGs.