Elasticsearch: Difference between “Term”, “Match Phrase”, and “Query String”

by

term query matches a single term as it is : the value is not analyzed.
So, it doesn’t have to be lowercased depending on what you have indexed.

If you provided Bennett at index time and the value is not analyzed, the following query won’t return anything :

{
  "query": {
    "term" : { "user" : "bennett" }
  }
}

match_phrase query will analyze the input if analyzers are defined for the queried field and find documents matching the following criteria:

  • all the terms must appear in the field
  • they must have the same order as the input value
  • there must not be any intervening terms, i.e. be consecutive (potentially excluding stop-words but this can be complicated)

For example, if you index the following documents (using standard analyzer for the field foo):

{ "foo":"I just said hello world" }

{ "foo":"Hello world" }

{ "foo":"World Hello" }

{ "foo":"Hello dear world" }

This match_phrase query will only return the first and second documents :

{
  "query": {
    "match_phrase": {
      "foo": "Hello World"
    }
  }
}

query_string query search, by default, on a _all field which contains the text of several text fields at once. On top of that, it’s parsed and supports some operators (AND/OR…), wildcards and so on (see related syntax).

As the match_phrase queries, the input is analyzed according to the analyzer set on the queried field.

Unlike the match_phrase, the terms obtained after analysis don’t have to be in the same order, unless the user has used quotes around the input.

For example, using the same documents as before, this query will return all the documents :

{
  "query": {
    "query_string": {
      "query": "hello World"
    }
  }
}

But this query will return the same 2 documents as the match_phrase query :

{
  "query": {
    "query_string": {
      "query": "\"Hello World\""
    }
  }
}

There is much more to say about the different options for those queries, please take a look at the related documentation :

Hope this is clear enough and it will help.

More Related Contents:

  1. Elasticsearch replication of other system data?
  2. How to search for a part of a word with ElasticSearch
  3. no [query] registered for [filtered]
  4. ES keeps returning every document
  5. Elasticsearch: Failed to connect to localhost port 9200 – Connection refused
  6. Calculating time between events
  7. Make elasticsearch only return certain fields?
  8. Remove duplicate documents from a search in Elasticsearch
  9. Elasticsearch 2.1: Result window is too large (index.max_result_window)
  10. Max limit on the number of values I can specify in the ids filter or generally query clause?
  11. How to update multiple documents that match a query in elasticsearch
  12. Elasticsearch searchable synthetic fields
  13. Why do I need “store”:”yes” in elasticsearch?
  14. Change default mapping of string to “not analyzed” in Elasticsearch
  15. How to not-analyze in ElasticSearch?
  16. Save Spark Dataframe into Elasticsearch – Can’t handle type exception
  17. elasticsearch – what to do with unassigned shards
  18. How to retrieve unique count of a field using Kibana + Elastic Search
  19. FIELDDATA Data is too large
  20. Can We Retrieve Previous _source Docs with Elastic Search Versions
  21. Elasticsearch, Tire, and Nested queries / associations with ActiveRecord
  22. ElasticSearch: Unassigned Shards, how to fix?
  23. Content-Type header [application/x-www-form-urlencoded] is not supported on Elasticsearch
  24. Elasticsearch, Failed to obtain node lock, is the following location writable
  25. low disk watermark [??%] exceeded on
  26. Elasticsearch – set max_clause_count
  27. How to bind Elasticsearch 2.0 on both Loopback and Non-Loopback interfaces?
  28. How to use the official docker elasticsearch container?
  29. Remove a field from a Elasticsearch document
  30. How to create multiple indexes in logstash.conf file?

Leave a Comment