-
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
INGEST: Make a few Processors callable by Painless #32170
INGEST: Make a few Processors callable by Painless #32170
Conversation
original-brownbear
commented
Jul 18, 2018
- Extracted a few stateless String processors as well as the json processor to static methods and whitelisted them in Painless
* Extracted a few stateless String processors as well as the json processor to static methods and whitelisted them in Painless
Pinging @elastic/es-core-infra |
@rjernst just looking for a quick confirmation that this (putting all the stateless things behind on a single |
Thanks @original-brownbear. This is generally what I was thinking. The only caveat is I would try to keep the implementations in the processors themselves as static methods, and have the static methods on Processors call the static methods on the implementation classes. In the future, when we have static imports, Processors can then just go away, static importing from each class. |
@rjernst yea
I'd like the same but can't really do that I'm afraid :( The processors all live in |
Yes, it is possible. See the painless whitelist example plugin. |
@rjernst alright done I think. Let me know if this is the right approach. There's actually not that many processors left that make sense to expose here (the others either have some state and would be inefficient to expose for now or they're just simple |
@rjernst Can you take another look here when you have a sec? Merging this one would also allow opening a clean PR for my drop solution I wrote up yesterday (that kinda needs the whole whitelisting magic added here for the |
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.
Thanks for the changes. LGTM.
@rjernst np + thanks for the review => drop call incoming :). Also, just |
I think this can go to 6.x. |
* INGEST: Make a few Processors callable by Painless * Extracted a few stateless String processors as well as the json processor to static methods and whitelisted them in Painless * provide whitelist from processors plugin
* es/master: (23 commits) Switch full-cluster-restart to new style Requests (#32140) [DOCS] Clarified that you must remove X-Pack plugin when upgrading from pre-6.3. (#32016) Remove BouncyCastle dependency from runtime (#32193) INGEST: Extend KV Processor (#31789) (#32232) INGEST: Make a few Processors callable by Painless (#32170) Add region ISO code to GeoIP Ingest plugin (#31669) [Tests] Remove QueryStringQueryBuilderTests#toQuery class assertions (#32236) Make sure that field aliases count towards the total fields limit. (#32222) Switch rolling restart to new style Requests (#32147) muting failing test for internal auto date histogram to avoid failure before fix is merged MINOR: Remove unused `IndexDynamicSettings` (#32237) Fix multi level nested sort (#32204) Enhance Parent circuit breaker error message (#32056) [ML] Use default request durability for .ml-state index (#32233) Remove indices stats timeout from monitoring docs Rename ranking evaluation response section (#32166) Dependencies: Upgrade to joda time 2.10 (#32160) Remove aliases resolution limitations when security is enabled (#31952) Ensure that field aliases cannot be used in multi-fields. (#32219) TESTS: Check for Netty resource leaks (#31861) ...