Hi, when thinking further about it it's clear that https://issues.apache.org/jira/browse/SOLR-433 would be even better - we could generate the spellechecker indices on commit/optimize on the master and replicate them to all slaves.
Just wondering what's the reason that this patch receives that little interest. Anything wrong with it? Cheers, Martin On Mon, Dec 13, 2010 at 2:04 AM, Martin Grotzke <martin.grot...@googlemail.com> wrote: > Hi, > > the spellchecker component already provides a buildOnCommit and > buildOnOptimize option. > > Since we have several spellchecker indices building on each commit is > not really what we want to do. > Building on optimize is not possible as index optimization is done on > the master and the slaves don't even run an optimize but only fetch > the optimized index. > > Therefore I'm thinking about an extension of the spellchecker that > allows you to rebuild the spellchecker based on a cron-expression > (e.g. rebuild each night at 1 am). > > What do you think about this, is there anybody else interested in this? > > Regarding the lifecycle, is there already some executor "framework" or > any regularly running process in place, or would I have to pull up my > own thread? If so, how can I stop my thread when solr/tomcat is > shutdown (I couldn't see any shutdown or destroy method in > SearchComponent)? > > Thanx for your feedback, > cheers, > Martin > -- Martin Grotzke http://www.javakaffee.de/blog/
