Inconsistent results for the text_phrase_prefix search

frazer · October 12, 2011, 12:53pm

I seem to be getting inconsistent/unpredictable results for the
text_phrase_prefix search on 0.17.8 that im using for an
autocomplete. I have supplied an example in the following gist.
Maybe I'm miss understanding how the query works.

gist.github.com

https://gist.github.com/frazerh/1281147

elastic_text_phrase_search

From Docs: max_expansions parameter that can control to how many prefixes the last term will be expanded. It is highly recommended to set it to an acceptable value to control the execution time of the query.

curl -X DELETE localhost:9200/cities
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Gabriel" }' 
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Gwann" }' 
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Carlos" }'
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Cristobal" }'
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Clemente" }'
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Diego" }'
curl -X POST "http://localhost:9200/cities/city" -d '{ "city" : "San Dimas" }'

This file has been truncated. show original

Please note that each time i delete and recreate this index I'm
getting different results for the text_phrase_prefix search examples
in the gist. Should they be consistent?

Thanks

Frazer

kimchy · October 12, 2011, 9:21pm

This realtes to the document distributed across the shards. You use auto
generates ids, which means each time, the documents will end up in different
shards. Thats fine, but, a score of a document is, by default, computed
against the documents that exists within the same shard (its "local" to the
shard). If you want more "correct" results, with scoring the spans the
cluster, you can set the search_type to dfs_query_then_fetch, though, it is
a slower search.

On Wed, Oct 12, 2011 at 2:53 PM, frazer frazer.horn@gmail.com wrote:

I seem to be getting inconsistent/unpredictable results for the
text_phrase_prefix search on 0.17.8 that im using for an
autocomplete. I have supplied an example in the following gist.
Maybe I'm miss understanding how the query works.

Elasticsearch text phrase prefix search with expansion · GitHub

Please note that each time i delete and recreate this index I'm
getting different results for the text_phrase_prefix search examples
in the gist. Should they be consistent?

Thanks

Frazer

SG1 · May 9, 2013, 12:48pm

Hi Kimchy,

I am facing same kind of issue without specifying the max_expansion. From the document I understood that "unbound" is the default for max_expansion.

I have around 5000000 of records and I am using text_phrase_prefix WITHOUT max_expansion. But when I search for single word it resulted properly. But the when I do the search with multiple words with partial second or third word like "San f" then I am not getting the result even I am not getting any max clause exception. If I have set the max_expansion to 10000 then results are coming properly.

Why default value "unbound" is not considered for max_expansion. I would appreciate your suggestion for this.

Note: I am using latest Elastic Search Version.

Thanks

Topic		Replies	Views
Why does elasticsearch return inconsistent result on version 7.8.1 and return correct result on 5.6.7 for the same match_phrase_prefix query? How can i get consistent result on elasticsearch 7.8.1? Elasticsearch	8	1194	January 14, 2022
The relation of the amount of indexed documents, max_expansions and prefix_length in text_phrase_prefix Elasticsearch	2	359	July 6, 2017
Match_phrase_prefix acts erratically when there is a filter Elasticsearch	5	1611	July 5, 2017
Text_phrase_prefix not giving the required results, the syntax is exactly as explained at "http://www.elasticsearch.org/guide/reference/query-dsl/text-query.html" Elasticsearch	2	261	July 6, 2017
ES gives very different scores, in match_phrase_prefix, for similar documents even I use DfsQueryThenFetch Elasticsearch	1	417	July 6, 2017

Inconsistent results for the text_phrase_prefix search

Related topics