Skip to content
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

Consolidate processor configurations for actions when there're key conflicts #4177

Open
oeyh opened this issue Feb 22, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@oeyh
Copy link
Collaborator

oeyh commented Feb 22, 2024

Is your feature request related to a problem? Please describe.
These processors have similar overwrite_if_key_exists options:

  • add_entries
  • copy_values
  • rename_keys
  • parse_json
  • parse_ion
  • key_value

grok processor has a keys_to_overwrite option so that you can determine to overwrite or append (default) for each grok generated field.

There are 3 basic options when adding fields but the key already exists: overwrite, append or skip. We should consider making the options available and consistent throughout processors.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.

Additional context
See comments from #4143

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants