Support for specifying ingest pipelines in Elasticsearch #744
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
Signed-off-by: Aleksandrov Aleksandr <[email protected]>
aa1ex
force-pushed
the
735-elastic-ingest-pipeline
branch
from
717781b to
0593d95
Compare
aa1ex
changed the title
Signed-off-by: Aleksandrov Aleksandr <[email protected]>
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
kirillov6
reviewed
Jan 28, 2025
Signed-off-by: Aleksandrov Aleksandr <[email protected]>
HeadHunter483
approved these changes
Jan 28, 2025
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.
Description
This PR implements the ability to specify an Elasticsearch ingest pipeline when sending data to an index. The change enables users to apply preprocessing or transformations to their data directly within Elasticsearch before indexing. This enhancement aligns with issue #735 and improves the flexibility and functionality of the Elasticsearch output plugin.