Add pipeline support to Ingest API #6070
Merged
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.
Replaces #6034 since merging into master would break tests due to dependency on ES master.
Requires #5656 and a build of Elasticsearch with the ingest functionality (at time of writing, a build of the master branch)
This PR adds pipeline support to the ingest API.
If you like Postman, import this collection with example requests to play around with.
An array of processors can be included under a
pipeline
key in the JSON payload provided to the POST endpoint. The Kibana ingest API will use this list of processors to create an ES ingest pipeline. As a result, you'll need to test this PR against a build from ES master (or clone the ES repo and rungradle run
).I've created a ticket to add API tests once Kibana master has been updated to track ES master (#6035).