-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Proposed changes to revise current/ingest.html . . . #28212
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,26 +3,27 @@ | |
|
||
[partintro] | ||
-- | ||
You can use ingest node to pre-process documents before the actual indexing takes place. | ||
This pre-processing happens by an ingest node that intercepts bulk and index requests, applies the | ||
transformations, and then passes the documents back to the index or bulk APIs. | ||
Use an ingest node to pre-process documents before the actual document indexing takes place. | ||
The ingest node intercepts bulk and index requests, it applies transformations, and it then | ||
passes the documents back to the index or bulk APIs. | ||
|
||
You can enable ingest on any node or even have dedicated ingest nodes. Ingest is enabled by default | ||
on all nodes. To disable ingest on a node, configure the following setting in the `elasticsearch.yml` file: | ||
All nodes enable ingest by default, so any node can handle ingest tasks. You can also create | ||
dedicated ingest nodes. To disable ingest for a node, configure the following setting in the | ||
elasticsearch.yml file: | ||
|
||
[source,yaml] | ||
-------------------------------------------------- | ||
node.ingest: false | ||
-------------------------------------------------- | ||
|
||
To pre-process documents before indexing, you <<pipeline,define a pipeline>> that specifies | ||
a series of <<ingest-processors,processors>>. Each processor transforms the document in some way. | ||
For example, you may have a pipeline that consists of one processor that removes a field from | ||
the document followed by another processor that renames a field. Configured pipelines are then stored | ||
in the <<cluster-state,cluster state>>. | ||
To pre-process documents before indexing, define a pipeline that specifies a series of | ||
processors. Each processor transforms the document in some specific way. For example, a | ||
pipeline might have one processor that removes a field from the document, followed by | ||
another processor that renames a field. The <<cluster-state,cluster state>> then stores | ||
the configured pipelines. | ||
|
||
To use a pipeline, you simply specify the `pipeline` parameter on an index or bulk request to | ||
tell the ingest node which pipeline to use. For example: | ||
To use a pipeline, simply specify the pipeline parameter on an index or bulk request. This | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The backtics around "pipeline" shouldn't be removed here, we use them to highlight json or url parameters (like in this case). |
||
way, the ingest node knows which pipeline to use. For example: | ||
|
||
[source,js] | ||
-------------------------------------------------- | ||
|
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.
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.
Can you keep the links to the pipeline and ingest-processor documentation? I think they are useful.