Hi Shane, While this initially seemed to be a good solution for my case, I have since moved away from it. A shingles filter alone significantly increases the size of an index. An n-gram filter only compounds this issue. Each shingle is n-grammed, and to get decent results you have to allow for large max n-grams. In my case, this led to an index that was too large, resulting in slower queries.
I am still using the shingle filter for basic search. It works great when a user is going to be searching for a portion of a string and you want phrase-like matching capabilities. On the other hand, I've found the Completion Suggester to be incredibly fast and efficient for autocomplete. Have a look here: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-completion.html Good luck! On Wednesday, April 23, 2014 2:54:13 PM UTC-4, Shane Neeley wrote: > > Any response on if this is a good way to do autocomplete? > >> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/646f5c2c-5e75-4d1b-9f8f-a1ba49558f59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
