On Tue, Jul 22, 2008 at 8:37 PM, Geoffrey Young <[EMAIL PROTECTED]> wrote:
> > > Shalin Shekhar Mangar wrote: > >> The problems you described in the spellchecker are noted in >> https://issues.apache.org/jira/browse/SOLR-622 -- I shall create an issue >> to >> synchronize spellcheck.build so that the index is not corrupted. >> > > I'd like to discuss this a little... > > I'm not sure that I want to rebuild the spelling index each time the > underlying data index changes - the process takes very long and my updates > are frequent changes to non-spelling related data. > > what I'd really like is for a change to my index to not cause an exception. > IIRC the "old" way of using a spellchecker didn't work like this at all - I > could completely rm data/index and leave data/spell in place, add new data, > not issue cmd=build and the spelling parts still worked just fine (albeit > with old data). > > not to say that SOLR-622 isn't a good idea (it is) but I don't really think > the entire solution is keeping the spellcheck index in sync. do they need > to be kept in sync for things not to implode on me? > > --Geoff > Sure, the intent of SOLR-622 is not to keep the two indices in sync, though it can certainly be used to do that. The intention is to avoid having to manually issue a build/reload command every time on startup. All the options introduced by SOLR-622 will be entirely optional and configurable so you will have the flexibility you want. Note that the SpellCheckComponent is similar to the old request handler in the way it manages the index. The spell checker index is separate from the main index and they do not need to be kept in sync, though I most users will probably use it that way. -- Regards, Shalin Shekhar Mangar.
