Adding the ability to skip the ingest pipeline #93016
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
masseyke
added
>enhancement
:Data Management/Ingest Node
|
Documentation preview: |
|
Hi @masseyke, I've created a changelog YAML for you. |
…arch into feature/skip-pipeline
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
…arch into feature/skip-pipeline
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new
skip_pipelineflag to index and upsert requests (including bulk). This flag tells Elasticsearch to not run the request pipeline or default pipeline. Elasticsearch will still run the final pipeline if one exists. This will enable Logstash to run pipelines before sending data to Elasticsearch, and not have Elasticsearch run them again.