The problem was that my test script did not pause between creating/populating the index, and searching on it. Even though there are very few documents (10), ElasticSearch still needs a second or two to catch its breath and mop its brow before it is ready to search.
Now to find a way to rank shorter strings higher than longer ones.... but that's another question.... thanks Lee On Wednesday, October 1, 2014 11:24:17 AM UTC+1, Lee Gee wrote: > > I have an ElasticSearch string field configured for autocomplete like this: > > autocomplete_analyzer: > type: custom > tokenizer: whitespace > filter: [ lowercase, asciifolding, ending_synonym, > name_synonyms, autocomplete_filter ] > > autocomplete_filter: > type: edge_ngram > min_gram: 1 > max_gram: 20 > token_chars: [ letter, digit, whitespace, punctuation, symbol ] > > search_analyzer: > type: custom > tokenizer: whitespace > filter: [ lowercase, asciifolding, standard, name_synonyms, > ending_synonym ] > > > > I have a record where the field contains 'S XYZ', and lots of other > records where the field contains other words beginning S. > > I do not understand why, when I search for 'S XYZ', it is not the first > result. > > Could someone please explain ? > > Many thanks in anticipation > lee > > -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c43961cb-224a-4b17-a03e-fc44926a05ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
