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

Expose ingest processor functionality within Painless #73346

Open
2 tasks done
danhermann opened this issue May 24, 2021 · 3 comments
Open
2 tasks done

Expose ingest processor functionality within Painless #73346

danhermann opened this issue May 24, 2021 · 3 comments
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Meta Team:Data Management Meta label for data/management team

Comments

@danhermann
Copy link
Contributor

danhermann commented May 24, 2021

Ingest processors that perform operations on inputs that are smaller than documents and return simple outputs should be exposed within Painless via static methods as the lowercase, uppercase, and JSON processors currently are.

@danhermann danhermann added :Core/Infra/Scripting Scripting abstractions, Painless, and Mustache Meta :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP labels May 24, 2021
@danhermann danhermann self-assigned this May 24, 2021
@elasticmachine elasticmachine added Team:Core/Infra Meta label for core/infra team Team:Data Management Meta label for data/management team labels May 24, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (Team:Core/Features)

@rjernst
Copy link
Member

rjernst commented May 27, 2021

Adding ingest processors as methods is much needed. Years ago we added many of them, but there many new processors were added since then.

Is there a specific list that should be added? Without that, this seems like an issue that is not actionable. Additionally, given the method customization options per scripting context, this shouldn't needed any changes in Painless (I'm going to remove the scripting label). If any issues do arise that need modifications in Painless, please create a new issue with the exact need, so that we can track it independently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Meta Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

3 participants