Hi Erick, thanx for your advice! I'll check the options with our client and see how we'll proceed. My spare time right now is already full with other open source stuff, otherwise it'd be fun contributing s.th. to solr! :-)
Cheers, Martin On Mon, Dec 13, 2010 at 2:46 PM, Erick Erickson <erickerick...@gmail.com> wrote: > *** > Just wondering what's the reason that this patch receives that little > interest. Anything wrong with it? > *** > > Nobody got behind it and pushed I suspect. And since it's been a long time > since it was updated, there's no guarantee that it would apply cleanly any > more. > Or that it will perform as intended. > > So, if you're really interested, I'd suggest you ping the dev list and ask > whether this is valuable or if it's been superseded. If the feedback is that > this > would be valuable, you can see what you can do to make it happen. > > Once it's working to your satisfaction and you've submitted a patch, let > people > know it's ready and ask them to commit it or critique it. You might have to > remind > the committers after a few days that it's ready and get it applied to trunk > and/or 3.x. > > But I really wouldn't start working with it until I got some feedback from > the > people who are actively working on Solr whether it's been superseded by > other functionality first, sometimes bugs just aren't closed when something > else makes it obsolete. > > Here's a place to start: http://wiki.apache.org/solr/HowToContribute > > Best > Erick > > On Mon, Dec 13, 2010 at 2:58 AM, Martin Grotzke < > martin.grot...@googlemail.com> wrote: > >> 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/ >> > -- Martin Grotzke http://www.javakaffee.de/blog/
