opensearch-project / opensearch-project/data-prepper
Migrate to use EventKey in processors
Open
Nobody has claimed this yet.
maintenance
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
This issue is for tracking migration of processors to use the new EventKey. See #1916 for more details.
-
mutate-event-processorsdelete_entries/rename_keys - #4636 -
mutate-event-processorsall others -
add_entries -
convert_type -
copy_values -
list_to_map -
map_to_list -
select_entries -
mutate-string-processors- #4649 -
user-agent-processor- #4628 -
drop-events-processor(does not need any keys) -
grok-processor -
key-value-processor -
parse-json-processor- #4842 -
split-event-processor -
aggregate-processor -
csv-processor -
decompress-processor -
dissect-processor -
flatten-processor -
geoip-processor -
obfuscate-processor -
translate-processor -
truncate-processor -
write-json-processor
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #1916 for the EventKey context, then inspect the unchecked processor entries listed here, such as grok-processor and add_entries. The migration is done when the remaining listed processors use EventKey; the completed checklist items and referenced issues show the expected tracking pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100