From 9cf721438066a8680637d3f647c903469827a57e Mon Sep 17 00:00:00 2001 From: Chris Earle Date: Tue, 18 Oct 2016 11:56:18 -0400 Subject: [DOCS] Add "version" to template and pipeline docs (#20407) * [DOCS] Add "version" to template and pipeline docs This adds details about the "version" to both the template and pipeline pages. --- docs/reference/ingest/ingest-node.asciidoc | 52 +++++++++++++++++++++++++++++- 1 file changed, 51 insertions(+), 1 deletion(-) (limited to 'docs/reference/ingest') diff --git a/docs/reference/ingest/ingest-node.asciidoc b/docs/reference/ingest/ingest-node.asciidoc index 013275c046..d905d84e33 100644 --- a/docs/reference/ingest/ingest-node.asciidoc +++ b/docs/reference/ingest/ingest-node.asciidoc @@ -90,6 +90,56 @@ For each returned pipeline, the source and the version are returned. The version is useful for knowing which version of the pipeline the node has. You can specify multiple IDs to return more than one pipeline. Wildcards are also supported. +[float] +[[versioning-pipelines]] +==== Pipeline Versioning + +Pipelines can optionally add a `version` number, which can be any integer value, +in order to simplify pipeline management by external systems. The `version` +field is completely optional and it is meant solely for external management of +pipelines. To unset a `version`, simply replace the pipeline without specifying +one. + +[source,js] +-------------------------------------------------- +PUT _ingest/pipeline/my-pipeline-id +{ + "description" : "describe pipeline", + "version" : 123, + "processors" : [ + { + "set" : { + "field": "foo", + "value": "bar" + } + } + ] +} +-------------------------------------------------- +// CONSOLE + +To check for the `version`, you can +<> +using `filter_path` to limit the response to just the `version`: + +[source,js] +-------------------------------------------------- +GET /_ingest/pipeline/my-pipeline-id?filter_path=*.version +-------------------------------------------------- +// TEST[continued] + +This should give a small response that makes it both easy and inexpensive to parse: + +[source,js] +-------------------------------------------------- +{ + "my-pipeline-id" : { + "version" : 123 + } +} +-------------------------------------------------- +// TESTRESPONSE + [[delete-pipeline-api]] === Delete Pipeline API @@ -1639,4 +1689,4 @@ pipeline should be used: -------------------------------------------------- The reason for this is that Ingest doesn't know how to automatically cast -a scalar field to an object field. \ No newline at end of file +a scalar field to an object field. -- cgit v1.2.3