Remove limiting condition #1017
Merged
Conversation
This file contains 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
stheppi
approved these changes
Jan 2, 2024
davidsloan
force-pushed
the
feat/remove-slash-limitation
branch
from
e99d98d to
ba2ec27
Compare
davidsloan
force-pushed
the
feat/remove-slash-limitation
branch
from
ba2ec27 to
250acf8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cloud sinks (AWS S3, GCP Storage and Datalake) have a validation condition that prevents nested prefixes from being used.
This condition no longer seems to be needed and prevents more flexible behaviour, so in this PR, it has been removed.