lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Otis Gospodnetic (JIRA)" <>
Subject [jira] [Resolved] (SOLR-433) MultiCore and SpellChecker replication
Date Mon, 29 Oct 2012 06:51:16 GMT


Otis Gospodnetic resolved SOLR-433.

    Resolution: Won't Fix

I think this is no longer needed, since spellchecker no longer needs a separate index.  Resolving
as Won't Fix.
> MultiCore and SpellChecker replication
> --------------------------------------
>                 Key: SOLR-433
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: replication (scripts), spellchecker
>    Affects Versions: 1.3
>            Reporter: Otis Gospodnetic
>             Fix For: 4.1
>         Attachments: RunExecutableListener.patch, solr-433.patch, SOLR-433.patch, SOLR-433.patch,
SOLR-433.patch, SOLR-433.patch, SOLR-433-r698590.patch, SOLR-433_unified.patch, spellindexfix.patch
> With MultiCore functionality coming along, it looks like we'll need to be able to:
>   A) snapshot each core's index directory, and
>   B) replicate any and all cores' complete data directories, not just their index directories.
> Pulled from the "spellchecker and multi-core index replication" thread -
> Otis:
> I think that makes sense - distribute everything for a given core, not just its index.
 And the spellchecker could then also have its data dir (and only index/ underneath really)
and be replicated in the same fashion.
> Right?
> Ryan:
> Yes, that was my thought.  If an arbitrary directory could be distributed, then you could
>   /path/to/dist/index/...
>   /path/to/dist/spelling-index/...
>   /path/to/dist/foo
> and that would all get put into a snapshot.  This would also let you put multiple cores
within a single distribution:
>   /path/to/dist/core0/index/...
>   /path/to/dist/core0/spelling-index/...
>   /path/to/dist/core0/foo
>   /path/to/dist/core1/index/...
>   /path/to/dist/core1/spelling-index/...
>   /path/to/dist/core1/foo

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message