This could easily be done outside of Solr, too. Ie create a standalone command-line tool that opens an IndexWriter on the index, using a custom DeletionPolicy that deletes the "future" commits.
The TestDeletionPolicy#testOpenPriorSnapshot unit test (in oal.index) has an example of how to do this. It would also be possible, if we did this in Solr, to open a prior commit point, make changes against that, and commit new commit points, all without removing any of the future commit points; sort of like cutting a branch from an old revision in a source control system. Mike McCandless http://blog.mikemccandless.com On Tue, Sep 6, 2011 at 9:22 PM, Emmanuel Espina <[email protected]> wrote: > Apparently this feature does not exist so I copy the same mail I sent to > "user". What are your opinions on creating a Jira issue requesting this new > feature: > > With SolrDeletionPolicy you can chose the number of "versions" of the index > to store ( maxCommitsToKeep, it defaults to 1). Well, how can you revert to > an arbitrary version that you have stored? Is there anything in Solr or in > Lucene to pick the version of the index to load? > > The idea rose from a discussion with some fellows about "really paranoid > users" that want to keep several backup versions of the index and pick one > that worked in the past (after the index was corrupted in some way, probably > not immediately noticeable, and not having the possibility to re index the > data) > > Thank you > > Emmanuel --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
