[
https://issues.apache.org/jira/browse/SOLR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-658:
---------------------------------------
Attachment: SOLR-658.patch
This is cut out of the SOLR-561 patch supports loading index from an arbitrary
directory.
*Changes*
# A new method SolrCore#getNewIndexDir() is introduced which tries to read the
latest indexDir from index.properties file. If that file is not present the
default value (dataDir + "index/")
# SolrIndexSearcher now stores the path (indexDir) on which it is opened and
has a getter for it.
# When SolrCore#getIndexDir() is called, it gives the current searcher's index
directory, failing which the default value is given
# SolrIndexSearcher is always created with getNewIndexDir() and UpdateHandler
also uses getNewIndexDir() to open IndexWriter instances.
TODO:
* Add a test
* Add feature for loading arbitrary commit point.
> Allow Solr to load index from arbitrary directory in dataDir and Commit point
> -----------------------------------------------------------------------------
>
> Key: SOLR-658
> URL: https://issues.apache.org/jira/browse/SOLR-658
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.4
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.4
>
> Attachments: SOLR-658.patch
>
>
> This is a requirement for java based Solr replication
> Usecase for arbitrary index directory:
> if the slave has a corrupted index and the filesystem does not allow
> overwriting files in use (NTFS) replication will fail. The solution is to
> copy the index from master to an alternate directory on slave and load
> indexreader/indexwriter from this alternate directory.
> Usecase for arbitrary commitpoint :
> Replication can also provide rollback feature . The rollback should be able
> to mention a comitpoint /generation so that rollback is possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
