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 Sokolov <msoko...@safaribooksonline.com> wrote: > 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 Underwood wrote: >> 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 >> <msoko...@safaribooksonline.com> wrote: >> >>> 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 they did rebuild after >>>> restart. >>>> >>>> We’re running 4.7 and our dictionaries are configured like this. We do >>>> this for several fields. >>>> >>>> <lst name="suggester"> >>>> <str name="name">fieldName</str> >>>> <str name="lookupImpl">FuzzyLookupFactory</str> >>>> <str name="dictionaryImpl">DocumentDictionaryFactory</str> >>>> <str name="field">fieldName</str> >>>> <str name="weightField">qualityScore</str> >>>> <str name="suggestAnalyzerFieldType">string</str> >>>> <str name="buildOnCommit">true</str> >>>> </lst> >>>> wunder >>>> Walter Underwood >>>> wun...@wunderwood.org >>>> http://observer.wunderwood.org/ >>>> >>>> >
