From d0301e31be2a915b8e8d097e537fe0b30cc7e93c Mon Sep 17 00:00:00 2001 From: Owais Kazi Date: Wed, 8 May 2024 09:11:17 -0700 Subject: [PATCH] Updated documentation for using search pipeline for multiple indices (#7053) * Updated documentation for using search pipeline for multiple indices Signed-off-by: owaiskazi19 * Doc review complete with edits for clarity Signed-off-by: Melissa Vagi * Update using-search-pipeline.md Signed-off-by: Melissa Vagi Signed-off-by: Melissa Vagi --------- Signed-off-by: owaiskazi19 Signed-off-by: Melissa Vagi Co-authored-by: Melissa Vagi --- .../search-pipelines/using-search-pipeline.md | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/_search-plugins/search-pipelines/using-search-pipeline.md b/_search-plugins/search-pipelines/using-search-pipeline.md index 882c94d99e..ecb988ad11 100644 --- a/_search-plugins/search-pipelines/using-search-pipeline.md +++ b/_search-plugins/search-pipelines/using-search-pipeline.md @@ -130,6 +130,53 @@ The response contains only the public document, indicating that the pipeline was ``` +You can search across multiple indexes that share the same default pipeline. For example, `alias1` has two indexes, `my_index1` and `my_index2`, both of which have the default pipeline `my_pipeline` attached to them: + +```json +GET /alias1/_search +``` +{% include copy-curl.html %} + +The response includes only the public version of the document, confirming that the default pipeline was successfully applied: + +
+ + Response + + {: .text-delta} + +```json +{ + "took": 59, + "timed_out": false, + "_shards": { + "total": 2, + "successful": 2, + "skipped": 0, + "failed": 0 + }, + "hits": { + "total": { + "value": 1, + "relation": "eq" + }, + "max_score": 0.0, + "hits": [ + { + "_index": "my_index1", + "_id": "1", + "_score": 0.0, + "_source": { + "message": "This is a public message", + "visibility": "public" + } + } + ] + } +} +``` +
+ ### Disabling the default pipeline for a request If you want to run a search request without applying the default pipeline, you can set the `search_pipeline` query parameter to `_none`: