Yeah - I would want it fixed as a default setting of some sort, maybe
in-built in the Suggester class, so you wouldn't be required to have
something in config to make it work in a reasonable way. Glad my
insomnia went to some purpose.
-MIke
On 11/14/2014 02:12 PM, Walter Underwood wrote:
Tha
That fixed it.
I bet that would fix the problem with the very long startup that another user
had. That’s a bug in the default solrconfig.xml, it should persist the
dictionaries.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/
On Nov 14, 2014, at 12:42 AM, Michael
It looks like you have to define "storeDir", and if you don't then the
rebuild no longer happens, as you said. I think that goes in the config
block you showed, but I haven't tested this (we use a different
suggester with its own persistence strategy).
-Mike
On 11/14/14 2:01 AM, Walter Under
We get no suggestions until we force a build with suggest.build=true. Maybe we
need to define a spellchecker component to get that behavior?
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/
On Nov 13, 2014, at 10:56 PM, Michael Sokolov
wrote:
> I believe the spel
I believe the spellchecker component persists these indexes now and
reloads them on restart rather than rebuilding.
-Mike
On 11/13/14 7:40 PM, Walter Underwood wrote:
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since someone else had a problem because
We have to manually rebuild the suggest dictionaries after a restart. This
seems odd, since someone else had a problem because they did rebuild after
restart.
We’re running 4.7 and our dictionaries are configured like this. We do this for
several fields.
fieldName
FuzzyLookupF
