Skip to content
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

Merged
merged 4 commits into from
Oct 23, 2018

Conversation

original-brownbear
Copy link
Member

* Added documentation for Pipeline Processor
* Relates elastic#33188
@original-brownbear original-brownbear added >docs General docs changes :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v7.0.0 v6.5.0 labels Sep 5, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

| Name | Required | Default | Description
| `pipeline` | yes | - | The name of the pipeline to execute
|======

Copy link
Contributor

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

Copy link
Contributor

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).

@jakelandis
Copy link
Contributor

@original-brownbear - 2 minor suggestions, otherwise LGTM

@rjernst - did you want to review ?

--------------------------------------------------
{
"pipeline": {
"pipeline": "inner-pipeline"
Copy link
Member

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?

Copy link
Member Author

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?

Copy link
Member

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok incoming :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in #34733

@jakelandis jakelandis merged commit f79bdec into elastic:master Oct 23, 2018
jakelandis pushed a commit to jakelandis/elasticsearch that referenced this pull request Oct 23, 2018
* Added documentation for Pipeline Processor
* Relates elastic#33188
jakelandis pushed a commit that referenced this pull request Oct 24, 2018
* Added documentation for Pipeline Processor
* Relates #33188
@jakelandis
Copy link
Contributor

6.5 backport: 27ba45e

kcm pushed a commit that referenced this pull request Oct 30, 2018
* Added documentation for Pipeline Processor
* Relates #33188
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >docs General docs changes v6.5.0 v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants