Right. Sticking to index only processing here should resolve false matches
to 3116 by [3115].
The log should have OutOfMemoryError: heap blah or something. That's the
cause.
On Fri, Dec 29, 2017 at 5:27 PM, Siarhei Chystsiakou
wrote:
> Thank you for your answer.
>
> I tried to use EdgeNGram und
Hi Rick!
Yes, as soon as I get the required result I'll definitely publish it on
GitHub. Dovecot default scheme doesn't suit me, when I use it the search
works according to the full word, but I want to make it wildcard search. I
don't have the solution. Hope the this group will help me.
2017-12-
Siarhei:
Will you be putting up your system at github? I would like to Solr-ize my
dovecot.
Maybe you saw this already:
https://github.com/dovecot/core/blob/master/doc/solr-schema.xml
https://github.com/dovecot/core/blob/master/src/plugins/fts-solr/solr-connection.c
https://github.com/dovecot/c
Thank you for your answer.
I tried to use EdgeNGram under the same settings
the same problem emerged, the search was not exactly correct. For instance,
I need to find the figure 311570, I enter 3115 into the search bar, in the
result I get all the figures that start from 311 and not 3115. Shou
Obviously, Chris has nothing in common with Christmas, hence this classic
search behavior is correct.
What people are asking here is autocomplete, and it's a separate UX and
algorithms.
You can start to explore different aspects of this field from
https://lucidworks.com/2015/03/04/solr-suggester/
Y
Hi
Does anyone have any idea how to fix this?
2017-12-27 13:34 GMT+01:00 Siarhei Chystsiakou :
> Hi everybody!
> I try integration Solr 6.6.1 with my email server (dovecot 2.32). I have
> the following settings:
>
> schema.xml - https://pastebin.com/1XXWTs8V
> solrconfig.xml - https://pastebin
