You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the ability to require an ingest pipeline (#46847)
This commit adds the ability to require an ingest pipeline on an
index. Today we can have a default pipeline, but that could be
overridden by a request pipeline parameter. This commit introduces a new
index setting index.required_pipeline that acts similarly to
index.default_pipeline, except that it can not be overridden by a
request pipeline parameter. Additionally, a default pipeline and a
request pipeline can not both be set. The required pipeline can be set
to _none to ensure that no pipeline ever runs for index requests on that
index.
Copy file name to clipboardExpand all lines: docs/reference/index-modules.asciidoc
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -234,13 +234,20 @@ specific index module:
234
234
The length of time that a <<delete-versioning,deleted document's version number>> remains available for <<index-versioning,further versioned operations>>.
235
235
Defaults to `60s`.
236
236
237
-
`index.default_pipeline`::
237
+
`index.default_pipeline`::
238
238
239
239
The default <<ingest,ingest node>> pipeline for this index. Index requests will fail
240
240
if the default pipeline is set and the pipeline does not exist. The default may be
241
241
overridden using the `pipeline` parameter. The special pipeline name `_none` indicates
242
242
no ingest pipeline should be run.
243
243
244
+
`index.required_pipeline`::
245
+
The required <<ingest,ingest node>> pipeline for this index. Index requests
246
+
will fail if the required pipeline is set and the pipeline does not exist.
247
+
The required pipeline can not be overridden with the `pipeline` parameter. A
248
+
default pipeline and a required pipeline can not both be set. The special
249
+
pipeline name `_none` indicates no ingest pipeline will run.
0 commit comments