-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
ingest: document index.default_pipeline #34500
Conversation
Pinging @elastic/es-core-infra |
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.
LGTM
@original-brownbear - I forgot to call out this option in the ingest node documentation. Can you please take another look ? |
Still LGTM :) |
Is the override of |
Nope, it isn't mentioned. I can add to this PR. how about:
|
Updated PR to include mention of |
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.
Looks good, one suggestion.
|
||
The default <<ingest,ingest node>> pipeline for this index. Index requests will fail | ||
if the default pipeline is set and the pipeline does not exist. The default may be | ||
ignored per request by setting the request parameter `pipeline=_none`. |
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.
I suggestion something like this in place of the last sentence:
The default may be overridden using the `pipeline` parameter. The special pipeline name `_none` indicates no ingest pipeline should be run.
The point is to show that pipeline can be specified in general to override the default, and that _none
is just a special pipeline name.
6.5 backport: e0ee802 |
No description provided.