on here who can offer some more perspective on
this or a possible query analyzer that I haven't heard of that can solve
this issue (I would also be interested in that).
Nick
On Thu, May 5, 2016 at 6:33 PM, Lasitha Wattaladeniya
wrote:
> Hi nd,
>
> Here's the issue.. Let
We implemented something similar it sounds to what you are asking but I
dont see why you would need to match the original field. Since technically
a field that has *software engineer* indexed is matched by a query like
"software eng" to "software engineer" with the ngrams; which makes the
exac
If I am understanding you correctly, it sounds like you are looking for an
phrase match with a really large query slop parameter (qs,
https://cwiki.apache.org/confluence/display/solr/The+DisMax+Query+Parser#TheDisMaxQueryParser-Theqs%28QueryPhraseSlop%29Parameter),
I believe the old way of doing th
Hello,
I have been working on a project to modernize a search suggestion component
that currently relies on a spellchecker component to return suggestions to
the user. I want to move the suggester from the Spellchecker component
over to the Suggester search component but I have ran into a snag i