Feature "Autocomplete did-you-mean completion suggesters"

EntityType "Feature"

Keywords/Contexts

Elasticsearch

Annotations

RefersToElasticsearchDocumentation::https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters.html

[edit]

Main Page ‎ (← links)
Contexts ‎ (← links)
Template:EntitiesByEntityType ‎ (← links)
Property:HasEntityType ‎ (← links)
Property:HasEntityTitle ‎ (← links)
Property:HasEntityKeyword ‎ (← links)
Property:HasEntityTypeAndEntityTitle ‎ (← links)
Feature ‎ (← links)
Elasticsearch ‎ (← links)
Property:RefersToElasticsearchDocumentation ‎ (← links)

[edit]

See below…

_search?typed_keys takes a suggest section on the same level as query and _source.

Story

TypeAhead and Search are run against tokens:

in specific fields of specific predicates ("PredicateFieldsFacet", currently specified in{" "} typeaheadAndSearchThesePredicates)
of specific documents ("DocumentsFacet", currently specified in es.search(taquery, index_alias))

The suggest section contains multiple named suggesters which specify:

the text to check for suggestions (or it can be taken from the global suggest text field),
which field to check and
how to check the field (term, phrase, completion/context).

The suggest section and the query are independent of each other.

The search result will contain a section suggest on the same level as hits. The suggest section will contain the results for each named suggester specifying:

the text that was checked and
an array of suggested scored options.

Did-you-mean/Spell-correction

Completion/Autocomplete/Typeahead

HasEntityTitle

For "dock tok" autocomplete should match "Delete Docker authentication token".

 {
   "_source": {
     "includes": [
       "HasEntityTitle"
     ],
     "excludes": []
   },
   "query": {
     "match": {
       "HasEntityTitle.completion": {
         "query": "dock tok",
         "operator": "and"
       }
     }
   },
   "highlight": {
     "fields": {
       "HasEntityTitle.completion": {}
     }
   }
 }

Keyword

HasEntityType

Predicate

In dataspects predicates are CamelCased. E.g. for "CanBeDeveloped" autocomplete should match on case-insensitive "can", "dev", "can dev" and "dev can".

 {
   "size": 0,
   "query": {
     "match": {
       "predicate.completion": {
         "query": "can be",
         "operator": "and"
       }
     }
   },
   "highlight": {
     "fields": {
       "predicate.completion": {}
     }
   },
   "aggs": {
     "entityTypes": {
       "terms": {
         "field": "predicate.keyword"
       }
     }
   }
 }

Where should the completion text come from?

Past user queries (problematic)
Text of the content being searched (better)

Completions based on the text of the content being searched

Which fields?
How analyze the text?
- Preserve readability
- Support phrase suggestions
Construct completion search