Mixing exact search with stemming

When building a search application, stemming is often a must as it is desirable for a query on skiing to match documents that contain ski or skis. But what if a user wants to search for skiing specifically? The typical way to do this would be to use a multi-field in order to have the same content indexed in two different ways:

  1. PUT index
  2. {
  3.   "settings": {
  4.     "analysis": {
  5.       "analyzer": {
  6.         "english_exact": {
  7.           "tokenizer": "standard",
  8.           "filter": [
  9.             "lowercase"
  10.           ]
  11.         }
  12.       }
  13.     }
  14.   },
  15.   "mappings": {
  16.     "properties": {
  17.       "body": {
  18.         "type": "text",
  19.         "analyzer": "english",
  20.         "fields": {
  21.           "exact": {
  22.             "type": "text",
  23.             "analyzer": "english_exact"
  24.           }
  25.         }
  26.       }
  27.     }
  28.   }
  29. }
  31. PUT index/_doc/1
  32. {
  33.   "body": "Ski resort"
  34. }
  36. PUT index/_doc/2
  37. {
  38.   "body": "A pair of skis"
  39. }
  41. POST index/_refresh

With such a setup, searching for ski on body would return both documents:

  1. GET index/_search
  2. {
  3.   "query": {
  4.     "simple_query_string": {
  5.       "fields": [ "body" ],
  6.       "query": "ski"
  7.     }
  8.   }
  9. }
  1. {
  2.   "took": 2,
  3.   "timed_out": false,
  4.   "_shards": {
  5.     "total": 1,
  6.     "successful": 1,
  7.     "skipped" : 0,
  8.     "failed": 0
  9.   },
  10.   "hits": {
  11.     "total" : {
  12.         "value": 2,
  13.         "relation": "eq"
  14.     },
  15.     "max_score": 0.18232156,
  16.     "hits": [
  17.       {
  18.         "_index": "index",
  19.         "_type": "_doc",
  20.         "_id": "1",
  21.         "_score": 0.18232156,
  22.         "_source": {
  23.           "body": "Ski resort"
  24.         }
  25.       },
  26.       {
  27.         "_index": "index",
  28.         "_type": "_doc",
  29.         "_id": "2",
  30.         "_score": 0.18232156,
  31.         "_source": {
  32.           "body": "A pair of skis"
  33.         }
  34.       }
  35.     ]
  36.   }
  37. }

On the other hand, searching for ski on body.exact would only return document 1 since the analysis chain of body.exact does not perform stemming.

  1. GET index/_search
  2. {
  3.   "query": {
  4.     "simple_query_string": {
  5.       "fields": [ "body.exact" ],
  6.       "query": "ski"
  7.     }
  8.   }
  9. }
  1. {
  2.   "took": 1,
  3.   "timed_out": false,
  4.   "_shards": {
  5.     "total": 1,
  6.     "successful": 1,
  7.     "skipped" : 0,
  8.     "failed": 0
  9.   },
  10.   "hits": {
  11.     "total" : {
  12.         "value": 1,
  13.         "relation": "eq"
  14.     },
  15.     "max_score": 0.8025915,
  16.     "hits": [
  17.       {
  18.         "_index": "index",
  19.         "_type": "_doc",
  20.         "_id": "1",
  21.         "_score": 0.8025915,
  22.         "_source": {
  23.           "body": "Ski resort"
  24.         }
  25.       }
  26.     ]
  27.   }
  28. }

This is not something that is easy to expose to end users, as we would need to have a way to figure out whether they are looking for an exact match or not and redirect to the appropriate field accordingly. Also what to do if only parts of the query need to be matched exactly while other parts should still take stemming into account?

Fortunately, the query_string and simple_query_string queries have a feature that solves this exact problem: quote_field_suffix. This tells Elasticsearch that the words that appear in between quotes are to be redirected to a different field, see below:

  1. GET index/_search
  2. {
  3.   "query": {
  4.     "simple_query_string": {
  5.       "fields": [ "body" ],
  6.       "quote_field_suffix": ".exact",
  7.       "query": "\"ski\""
  8.     }
  9.   }
  10. }
  1. {
  2.   "took": 2,
  3.   "timed_out": false,
  4.   "_shards": {
  5.     "total": 1,
  6.     "successful": 1,
  7.     "skipped" : 0,
  8.     "failed": 0
  9.   },
  10.   "hits": {
  11.     "total" : {
  12.         "value": 1,
  13.         "relation": "eq"
  14.     },
  15.     "max_score": 0.8025915,
  16.     "hits": [
  17.       {
  18.         "_index": "index",
  19.         "_type": "_doc",
  20.         "_id": "1",
  21.         "_score": 0.8025915,
  22.         "_source": {
  23.           "body": "Ski resort"
  24.         }
  25.       }
  26.     ]
  27.   }
  28. }

In the above case, since ski was in-between quotes, it was searched on the body.exact field due to the quote_field_suffix parameter, so only document 1 matched. This allows users to mix exact search with stemmed search as they like.

If the choice of field passed in quote_field_suffix does not exist the search will fall back to using the default field for the query string.