This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Corrected the tokenization logic in CassandraMetadataDAO #2953
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
…f the workflow name.
jxu-nflx
approved these changes
Apr 27, 2022
apanicker-nflx
approved these changes
Apr 27, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
INDEX_DELIMITERcould be part of the workflow name.Pull Request type
./gradlew generateLock saveLockto refresh dependencies)Changes in this PR
When the workflow name contains a
/, thegetAllWorkflowDefs()call fails because the tokenization logic does not account for it. Now the logic is updated to account for it.Alternatives considered
Considered adding a validation error for workflow names containing
/. But that would be artificial and not relevant for other persistence implementations.