This version of the OpenSearch documentation is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.

Search relevance

Search relevance evaluates the accuracy of the search results returned by a query. The higher the relevance, the better the search engine. Compare Search Results is the first search relevance feature in OpenSearch.

Compare Search Results

Compare Search Results is an experimental feature. For updates on the progress of Compare Search Results and other search relevance features, or if you want to leave feedback that could help improve the feature, join the discussion on the OpenSearch forum.

Compare Search Results in OpenSearch Dashboards lets you compare results from two queries side by side to determine whether one query produces better results than the other. Using this tool, you can evaluate search quality by experimenting with queries.

For example, you can see how results change when you apply one of the following query changes:

  • Weighting different fields differently
  • Different stemming or lemmatization strategies
  • Shingling

Prerequisites

Before you get started, you must index data in OpenSearch. To learn how to create a new index, see Index data.

Alternatively, you can add sample data in OpenSearch Dashboards using the following steps:

  1. On the top menu bar, go to OpenSearch Dashboards > Overview.
  2. Select View app directory.
  3. Select Add sample data.
  4. Choose one of the built-in datasets and select Add data.

Using Compare Search Results in OpenSearch Dashboards

To compare search results in OpenSearch Dashboards, perform the following steps.

Step 1: On the top menu bar, go to OpenSearch Plugins > Search Relevance.

Step 2: Enter the search text in the search bar.

Step 3: Select an index for Query 1 and enter a query (request body only) in OpenSearch Query DSL. The GET HTTP method and the _search endpoint are implicit. Use the %SearchText% variable to refer to the text in the search bar.

The following is an example query:

  1. {
  2.   "query": {
  3.     "multi_match": {
  4.       "query": "%SearchText%",
  5.       "fields": [ "description", "item_name" ]
  6.     }
  7.   }
  8. }

Step 4: Select an index for Query 2 and enter a query (request body only).

The following example query boosts the title field in search results:

  1. {
  2.   "query": {
  3.     "multi_match": {
  4.       "query": "%SearchText%",
  5.       "fields": [ "description", "item_name^3" ]
  6.     }
  7.   }
  8. }

Step 5: Select Search and compare the results in Result 1 and Result 2.

The following example screen shows a search for the word “cup” in the description and item_name fields with and without boosting the item_name:

Compare search results

If a result in Result 1 appears in Result 2, the Up and Down indicators below the result number signify how many places the result moved up or down compared to the same result in Result 2. In this example, the document with the ID 2 is Up 1 place in Result 2 compared to Result 1 and Down 1 place in Result 1 compared to Result 2.

Changing the number of results

By default, OpenSearch returns the top 10 results. To change the number of returned results to a different value, specify the size parameter in the query:

  1. {
  2.   "size": 15,
  3.   "query": {
  4.     "multi_match": {
  5.       "query": "%SearchText%",
  6.       "fields": [ "title^3", "text" ]
  7.     }
  8.   }
  9. }

Setting size to a high value (for example, larger than 250 documents) may degrade performance.

You cannot save a given comparison for future use, so Compare Search Results is not suitable for systematic testing.

Comparing OpenSearch search results with reranked results

One use case for Compare Search Results is the comparison of raw OpenSearch results with the same results processed by a reranking application. OpenSearch currently integrates with the following two rerankers:

Reranking results with Kendra Intelligent Ranking for OpenSearch

An example of a reranker is Kendra Intelligent Ranking for OpenSearch, contributed by the Amazon Kendra team. This plugin takes search results from OpenSearch and applies Amazon Kendra’s semantic relevance rankings calculated using vector embeddings and other semantic search techniques. For many applications, this provides better result rankings.

To try Kendra Intelligent Ranking, you must first set up the Amazon Kendra service. To get started, see Amazon Kendra. For detailed information, including plugin setup instructions, see Intelligently ranking OpenSearch (self managed) results using Amazon Kendra.

Comparing search results with reranked results in OpenSearch Dashboards

To compare search results with reranked results in OpenSearch Dashboards, enter a query in Query 1 and enter the same query using a reranker in Query 2. Then compare the search results from OpenSearch with reranked results.

The following example searches for the text “snacking nuts” in the abo index. The documents in the index contain snack descriptions in the bullet_point array.

OpenSearch Intelligent Ranking query

  1. Enter snacking nuts in the search bar.

  2. Enter the following query, which searches the bullet_point field for the search text “snacking nuts”, in Query 1:

    1.  {
    2.    "query": {
    3.      "match": {
    4.        "bullet_point": "%SearchText%"
    5.      }
    6.    },
    7.    "size": 25
    8.  }

  3. Enter the same query with a reranker in Query 2. This example uses Kendra Intelligent Ranking:

    1.  {
    2.    "query" : {
    3.      "match" : {
    4.        "bullet_point": "%SearchText%"
    5.      }
    6.    },
    7.    "size": 25,
    8.    "ext": {
    9.      "search_configuration":{
    10.        "result_transformer" : {
    11.          "kendra_intelligent_ranking": {
    12.            "order": 1,
    13.            "properties": {
    14.              "title_field": "item_name",
    15.              "body_field": "bullet_point"
    16.            }
    17.          }
    18.        }
    19.      }
    20.    }
    21.  }

    In the preceding query, body_field refers to the body field of the documents in the index, which Kendra Intelligent Ranking uses to rank the results. The body_field is required, while the title_field is optional.

  4. Select Search and compare the results in Result 1 and Result 2.

Personalizing search results with Amazon Personalize Search Ranking

Another example of a reranker is Amazon Personalize Search Ranking, contributed by the Amazon Personalize team. Amazon Personalize uses machine learning (ML) techniques to generate custom recommendations for your users. The plugin takes search results from OpenSearch and applies a search pipeline to rerank them according to their Amazon Personalize ranking. The Amazon Personalize rankings are based on the user’s past behavior and metadata about the search items and the user. This workflow improves the search experience for your users by personalizing their search results.

To try Amazon Personalize Search Ranking, you must first set up Amazon Personalize. To get started, see Amazon Personalize. For detailed information, including plugin setup instructions, see Personalizing search results from OpenSearch (self-managed).