lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-9865) RestoreCore failing can roll an index back in time.
Date Wed, 14 Dec 2016 18:50:58 GMT
Mark Miller created SOLR-9865:
---------------------------------

             Summary: RestoreCore failing can roll an index back in time.
                 Key: SOLR-9865
                 URL: https://issues.apache.org/jira/browse/SOLR-9865
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Mark Miller


Maybe I'm missing something, but I was just looking at RestoreCore and see that in some failure
cases it removes the index properties file to roll back to the existing index. But as far
as I know, you could have index index.timestamp1, index.timestamp2 and deleting that file
would roll you back to index instead of index.timestamp1.

In SOLR-9859, I'm wondering if we should automatically find the latest index directory if
no index.properties file exists, which I guess could be a solution here too if done right.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message