-
Notifications
You must be signed in to change notification settings - Fork 1.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
Conditional Response Processor #6715
Comments
@macohen can this issue be moved to search-processor? |
@noCharger commented in person that this could just be a specific ScriptResponseProcessor: #6713. If that's the case, I think putting effort into the scriptresponseprocessor and then seeing if we should have a specific processor that abstracts the choice made may be the right thing. Next step would be some info about how ScriptResponseProcessor could work for this case... |
If we want this to be consistent with ingest pipelines (which should be the guiding principle IMO), this wouldn't be a specific processor that users would add to their pipeline, but rather it would be a wrapper around another processor. See e.g. https://www.elastic.co/guide/en/elasticsearch/reference/7.10/ingest-conditionals.html |
duplicates #11782 |
As a user of search pipelines, I want to be able to insert conditional checks on the search response into my pipeline to inform what the pipeline should execute next.
The text was updated successfully, but these errors were encountered: