Thanks. I saw the "multicore" part of the issue title and disregarded
it. :-)
-Sean
Shalin Shekhar Mangar wrote:
We have SOLR-433 open. Not sure what needs to be done there.
On Fri, Aug 1, 2008 at 7:46 PM, Sean Timm <[EMAIL PROTECTED]> wrote:
Is there a recommended way to replicate the spell checker index from the
master to the slaves?
-Sean
Shalin Shekhar Mangar (JIRA) wrote:
[
https://issues.apache.org/jira/browse/SOLR-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
Shalin Shekhar Mangar updated SOLR-622:
---------------------------------------
Attachment: SOLR-622.patch
The last patch was generated incorrectly. Uploading new one.
We are introducing a configuration parameter for spell checker with this
issue
{code:xml}
<str name="buildOnCommit">true</str>
{code}
Now there is no need to check if a spell checker is built from Solr field
or not. If the configuration param is present, we can blindly build it on
newSearcher event.
SpellCheckComponent should build or load indices on startup and commits
-----------------------------------------------------------------------
Key: SOLR-622
URL: https://issues.apache.org/jira/browse/SOLR-622
Project: Solr
Issue Type: Improvement
Components: spellchecker
Affects Versions: 1.3
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
Priority: Minor
Fix For: 1.3
Attachments: SOLR-622.patch, SOLR-622.patch, SOLR-622.patch
SpellCheckComponent must be able to build/load spell check index on
startup and commits. With SOLR-605, SpellCheckComponent can register an
event listener for firstSearcher and newSearcher events and rebuild/reload
indices as appropriate.
* If index uses a FSDirectory and exists on disk then just reload it or
else build it on firstSearcher event.
* If index is built from a Solr field then re-build it on newSearcher
event.
This will help avoid having to add QuerySenderListener in configuration
and will not force people to issue build on first query.
All this should be configurable so that people who don't want to rebuild
on commits should be able to turn this feature off per configured spell
checker.