-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define multiple keys for type conversion #2934
Conversation
Signed-off-by: Haidong <whaidong@amazon.com>
Signed-off-by: Haidong <whaidong@amazon.com>
Signed-off-by: Haidong <whaidong@amazon.com>
Signed-off-by: Haidong <whaidong@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes looks good, just missing the documentation
Signed-off-by: Haidong <whaidong@amazon.com>
Ok, updated README |
* feat: add include_key options to KeyValueProcessor Signed-off-by: Haidong <whaidong@amazon.com> --------- Signed-off-by: Haidong <whaidong@amazon.com> Co-authored-by: Haidong <whaidong@amazon.com> Signed-off-by: rajeshLovesToCode <rajesh.dharamdasani3021@gmail.com>
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2934-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d93ead9f39588a3fb5d7c0d20df11a8875070fce
# Push it to GitHub
git push --set-upstream origin backport/backport-2934-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3 Then, create a pull request where the |
* feat: add include_key options to KeyValueProcessor Signed-off-by: Haidong <whaidong@amazon.com> --------- Signed-off-by: Haidong <whaidong@amazon.com> Co-authored-by: Haidong <whaidong@amazon.com> Signed-off-by: Marcos Gonzalez Mayedo <alemayed@amazon.com>
Description
Allow defining multiple keys in the convert_entry_type processor.
Note: existing key still works. But only One Of (key or Keys) is required.
If all of them defined or Non of them defined, will throw exception.
eg:
converts
{"message":"value","key1":"123", "key2":"456"}
to
{"message":"value","key1":123, "key2":456}
Issues Resolved
Resolve #2823
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.