-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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 Pipeline Processor #33418
INGEST: Document Pipeline Processor #33418
Conversation
original-brownbear
commented
Sep 5, 2018
- Added documentation for Pipeline Processor
- Relates ingest: Documentation improvements for ingest node #33188
* Added documentation for Pipeline Processor * Relates elastic#33188
Pinging @elastic/es-core-infra |
| Name | Required | Default | Description | ||
| `pipeline` | yes | - | The name of the pipeline to execute | ||
|====== | ||
|
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 I suggest to use pipelineA
and pipelineB
(or the like) as examples to avoid inner/outer which (to me at least) suggests a required relationship between the two pipelines.
} | ||
-------------------------------------------------- | ||
// TESTRESPONSE | ||
|
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.
It may also be of value to show the final document here (in addition to, or in replacement of the index reponse).
@original-brownbear - 2 minor suggestions, otherwise LGTM @rjernst - did you want to review ? |
-------------------------------------------------- | ||
{ | ||
"pipeline": { | ||
"pipeline": "inner-pipeline" |
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.
Looking at actual requests, this looks quite confusing having "pipeline" inside "pipeline" (we used to have similar for script
with the script query containing script
). I wonder if we could quickly rename the parameter to name
or something similar before 6.5 branch is cut?
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.
@rjernst sure that makes sense. Should I just do it in this PR or do you want a separate one?
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 would do a quick separate one, since this one is marked as docs.
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.
ok incoming :)
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.
Done in #34733
* Added documentation for Pipeline Processor * Relates elastic#33188
* Added documentation for Pipeline Processor * Relates #33188
6.5 backport: 27ba45e |
* Added documentation for Pipeline Processor * Relates #33188