From 88f3fbe3c25d28c58256cc1477c0c5e8e01fe095 Mon Sep 17 00:00:00 2001 From: Shubha Anjur Tupil Date: Wed, 1 Oct 2025 14:26:33 -0700 Subject: [PATCH 1/3] Update semantic search tutorial to include instructions on using the ELSER endpoint on EIS Update the semantic search tutorial to switch to the ELSER endpoint on EIS during tech preview --- .../search/semantic-search/semantic-search-semantic-text.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/solutions/search/semantic-search/semantic-search-semantic-text.md b/solutions/search/semantic-search/semantic-search-semantic-text.md index a81512886f..a635ba5850 100644 --- a/solutions/search/semantic-search/semantic-search-semantic-text.md +++ b/solutions/search/semantic-search/semantic-search-semantic-text.md @@ -42,6 +42,7 @@ PUT semantic-embeddings 1. The name of the field to contain the generated embeddings. 2. The field to contain the embeddings is a `semantic_text` field. Since no `inference_id` is provided, the default endpoint `.elser-2-elasticsearch` for the `elasticsearch` service is used. To use a different {{infer}} service, you must create an {{infer}} endpoint first using the [Create {{infer}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-inference-put) and then specify it in the `semantic_text` field mapping using the `inference_id` parameter. +3. To try the ELSER model on the Elastic Inference Service explicitly set the `inference_id` to `.elser-2-elastic`, see [Using `semantic_text` with ELSER on EIS](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#using-elser-on-eis) to learn how to set the `inference_id`. ::::{note} If you’re using web crawlers or connectors to generate indices, you have to [update the index mappings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping) for these indices to include the `semantic_text` field. Once the mapping is updated, you’ll need to run a full web crawl or a full connector sync. This ensures that all existing documents are reprocessed and updated with the new semantic embeddings, enabling semantic search on the updated data. @@ -156,4 +157,4 @@ POST /_query?format=txt * If you want to use `semantic_text` in hybrid search, refer to [this notebook](https://colab.research.google.com/github/elastic/elasticsearch-labs/blob/main/notebooks/search/09-semantic-text.ipynb) for a step-by-step guide. * For more information on how to optimize your ELSER endpoints, refer to [the ELSER recommendations](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md#elser-recommendations) section in the model documentation. -* To learn more about model autoscaling, refer to the [trained model autoscaling](../../../deploy-manage/autoscaling/trained-model-autoscaling.md) page. \ No newline at end of file +* To learn more about model autoscaling, refer to the [trained model autoscaling](../../../deploy-manage/autoscaling/trained-model-autoscaling.md) page. From 51e93194422d281759dae422d5ae92ce7e4ee7a5 Mon Sep 17 00:00:00 2001 From: Shubha Anjur Tupil Date: Wed, 1 Oct 2025 19:48:43 -0700 Subject: [PATCH 2/3] Update semantic-search-semantic-text.md making it a sentence after the code callout --- .../search/semantic-search/semantic-search-semantic-text.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/solutions/search/semantic-search/semantic-search-semantic-text.md b/solutions/search/semantic-search/semantic-search-semantic-text.md index a635ba5850..4bc43998e9 100644 --- a/solutions/search/semantic-search/semantic-search-semantic-text.md +++ b/solutions/search/semantic-search/semantic-search-semantic-text.md @@ -42,7 +42,8 @@ PUT semantic-embeddings 1. The name of the field to contain the generated embeddings. 2. The field to contain the embeddings is a `semantic_text` field. Since no `inference_id` is provided, the default endpoint `.elser-2-elasticsearch` for the `elasticsearch` service is used. To use a different {{infer}} service, you must create an {{infer}} endpoint first using the [Create {{infer}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-inference-put) and then specify it in the `semantic_text` field mapping using the `inference_id` parameter. -3. To try the ELSER model on the Elastic Inference Service explicitly set the `inference_id` to `.elser-2-elastic`, see [Using `semantic_text` with ELSER on EIS](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#using-elser-on-eis) to learn how to set the `inference_id`. + +To try the ELSER model on the Elastic Inference Service explicitly set the `inference_id` to `.elser-2-elastic`, see [Using `semantic_text` with ELSER on EIS](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#using-elser-on-eis) to learn how to set the `inference_id`. ::::{note} If you’re using web crawlers or connectors to generate indices, you have to [update the index mappings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping) for these indices to include the `semantic_text` field. Once the mapping is updated, you’ll need to run a full web crawl or a full connector sync. This ensures that all existing documents are reprocessed and updated with the new semantic embeddings, enabling semantic search on the updated data. From 84d182c39bfed15a77811adc39271421adb01088 Mon Sep 17 00:00:00 2001 From: Shubha Anjur Tupil Date: Wed, 1 Oct 2025 19:50:54 -0700 Subject: [PATCH 3/3] Update semantic-search-semantic-text.md --- .../search/semantic-search/semantic-search-semantic-text.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/search/semantic-search/semantic-search-semantic-text.md b/solutions/search/semantic-search/semantic-search-semantic-text.md index 4bc43998e9..4420ee96ac 100644 --- a/solutions/search/semantic-search/semantic-search-semantic-text.md +++ b/solutions/search/semantic-search/semantic-search-semantic-text.md @@ -43,7 +43,7 @@ PUT semantic-embeddings 1. The name of the field to contain the generated embeddings. 2. The field to contain the embeddings is a `semantic_text` field. Since no `inference_id` is provided, the default endpoint `.elser-2-elasticsearch` for the `elasticsearch` service is used. To use a different {{infer}} service, you must create an {{infer}} endpoint first using the [Create {{infer}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-inference-put) and then specify it in the `semantic_text` field mapping using the `inference_id` parameter. -To try the ELSER model on the Elastic Inference Service explicitly set the `inference_id` to `.elser-2-elastic`, see [Using `semantic_text` with ELSER on EIS](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#using-elser-on-eis) to learn how to set the `inference_id`. +To try the ELSER model on the Elastic Inference Service, explicitly set the `inference_id` to `.elser-2-elastic`. For instructions, refer to [Using `semantic_text` with ELSER on EIS](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#using-elser-on-eis). ::::{note} If you’re using web crawlers or connectors to generate indices, you have to [update the index mappings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping) for these indices to include the `semantic_text` field. Once the mapping is updated, you’ll need to run a full web crawl or a full connector sync. This ensures that all existing documents are reprocessed and updated with the new semantic embeddings, enabling semantic search on the updated data.