How to build an auto suggest function that works for multiple fields in
general? And how did they include a "kind" field in the result, to
determine where the hit comes from?
you may want to checkout the completion suggester, which allows you also to
add custom content to return by using payloads.
Also from my high level point of view, it merely looks like they are
maintaining an own suggest index instead of querying many others... (dont
know internals though)
How to build an auto suggest function that works for multiple fields in
general? And how did they include a "kind" field in the result, to
determine where the hit comes from?
How to build an auto suggest function that works for multiple fields in
general? And how did they include a "kind" field in the result, to
determine where the hit comes from?
@ddorian43: Thanks, I've already read their blog, but it has no ES
internals. @Alexander: Your guess was right, they're using an own suggest index. I've
posted my question to their blog and their answer came today:
The auto-suggest feature is totally disconnected from Elasticsearch. We
build a finite state transducer (FST) containing the most relevant of each
entity-type offline, and serve it from memory. The technique we use is
very similar to the one described here:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.