Skip to content

INGEST: Document Pipeline Processor#33418

Merged
jakelandis merged 4 commits intoelastic:masterfrom
original-brownbear:document-pipeline-proc
Oct 23, 2018
Merged

INGEST: Document Pipeline Processor#33418
jakelandis merged 4 commits intoelastic:masterfrom
original-brownbear:document-pipeline-proc

Conversation

@original-brownbear
Copy link
Copy Markdown
Contributor

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

Pinging @elastic/es-core-infra

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

Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
Contributor

@original-brownbear - 2 minor suggestions, otherwise LGTM

@rjernst - did you want to review ?

--------------------------------------------------
{
"pipeline": {
"pipeline": "inner-pipeline"
Copy link
Copy Markdown
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
Copy Markdown
Contributor 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
Copy Markdown
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
Copy Markdown
Contributor 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
Copy Markdown
Contributor 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
Copy Markdown
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

:Distributed/Ingest Node Execution or management of Ingest Pipelines >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