David,
Thank you for the response. I did indeed stumble upon an example using Lucene
4.x and used it only because that is what I’ve found, I see now that there are
examples in lucene-solr 5.x and 6.x. After your response I did some more
research and see all of the work that’s been done on
Hi All,
i am trying to retrieve most related results using user given search
queries. If there is no results for exact queries, i want to use term
modifiers during search time. And so, i want to give more importance to
term modifiers in the defined listed order given below
1. exact
Thank you for your prompt reply this makes perfect sense.
Le 07/06/2016 17:24, Robert Muir a écrit :
Its just a heuristic: that it does not allow 2 edits
(insertion/deletion/substitution/transposition) to the word if the
first character differs
Its just a heuristic: that it does not allow 2 edits
(insertion/deletion/substitution/transposition) to the word if the first
character differs (
https://github.com/apache/lucene-solr/blob/master/lucene/suggest/src/java/org/apache/lucene/search/spell/DirectSpellChecker.java#L411).
So when it goes
Hello,
I have a very strange behavior when I use the DirectSpellChecker of Lucene. I
have set the prefixLength to 0. I have indexed only one item with one field :
brand=samsung.
I have tried to make requests with spelling mistakes inside.
When I search for "smsng" I obtain "samsung" which is
Hello,
I have a very strange behavior when I use the DirectSpellChecker of
Lucene. I have set the prefixLength to 0. I have indexed only one item
with one field : brand=samsung.
I have tried to make requests with spelling mistakes inside.
When I search for "smsng" I obtain "samsung" which is
