-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Remove all fields other than a defined list #83010
Comments
Pinging @elastic/es-data-management (Team:Data Management) |
Sounds like a good enhancement request. However, we probably don't want to actually use reg-ex's here. Either a new keep processor (which is the opposite of remove) or a new field |
If this issue is beginner-friendly I would like to start my open source journey with this issue. |
@harshlancer, you are welcome to start working on this if you would like. I would suggest adding a new option to the existing remove processor rather than creating a whole new processor to perform this function. |
Sorry I don't think this issue is for a complete newbie.... |
Hi @danhermann |
Just to keep you guys posted: I am already working on the implementation of this issue, and I expect to raise a PR in 2 or 3 days. |
- Enhancement related to issue 83010 [elastic#83010]
Hi guys! |
Closed by #83665 |
Wouldn't make more sense to have a correct parser whatever Integration in the first place and not waste those computational resources on ingesting first wrong and delete after? |
This came up in a forum thread - https://discuss.elastic.co/t/reindex-identify-fields-to-remove-with-a-regular-expression/295275
The idea being that if you want to remove a bunch of fields, that you may not necessarily know the names of (or don't care), having a config option for the remove processor that you could simply define a set of fields to keep, thereyby removing everything else, would be a simple solution.
The text was updated successfully, but these errors were encountered: