However, Elasticsearch does provide context suggester to circumvent this issue up to some extent. I'm using elastic search 5.3 and to provide did-you-mean functionality, I want to limit the context of term or phrase suggester to only user's documents not all the documents in the index. The following parameters are supported for a geo context clause: A geo point object or a geo hash string to filter or boost the suggestion by. Queries like above go against this design.

This design facilitates faster searches through in-memory FST. Schema free: Some definitions, such as index, class, and field type, are not required before the indexing procedure, and when an object is indexed. To do this, you'll need the Context Suggester, which is built to add filtering.

If I query using only one Context ('location' in the above example) it gives an error, I need to pass both the contexts, is it possible to specify which context to use? Or pass something like a 'Context_Operation' parameter set to 'OR'. As already discussed, suggestions are stored in a separate data-structure - in-memory FST, whereas other fields are stored on disk. Term Suggester, Phrase Suggester, Completion Suggester, Context Suggester are the core components of its auto-completion and instant search capability. The Completion Suggester returns all results matching the input text. Then one that provide 'similar' term, based on the edit distance. Can we add an 'OR' operation on the contexts and/or specify which context to use for a particular query? Currently there are 4 types of suggesters in the Elasticsearch: Term suggester. I'm using context suggester and am wondering if we can set the scope of the context to be used for suggestions rather that using all contexts.Ĭurrently the query needs to match all contexts.

Context suggester elasticsearch