[
https://issues.apache.org/jira/browse/OAK-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615248#comment-15615248
]
Ian Boston edited comment on OAK-4943 at 10/28/16 12:30 PM:
------------------------------------------------------------
FYI: I am working on a Sling WebConsole UI to provide detail on all commits,
including the age of each commit and functionality to analyse each commit,
validate, rollback and download the commit. This is FYI as it doesn't fit
inside the Oak project and may be better in Sling or a contrib repo.
was (Author: ianeboston):
FYI: I am working on a Sling WebConsole UI to provide detail on all commits,
including age of each commit and functionality to analyse each commit,
validate, rollback and download the commit.
> Keep Lucene Commits so that if the Segments file gets corrupted recovery can
> be attempted.
> ------------------------------------------------------------------------------------------
>
> Key: OAK-4943
> URL: https://issues.apache.org/jira/browse/OAK-4943
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Affects Versions: 1.6
> Reporter: Ian Boston
>
> Currently, Lucene deletes all previous generations of the segments files as
> it has it uses the default IndexDeletionPolicy. Changing this to an
> IndexDeletionPolicy that keeps a number of previous segments files will allow
> an operator to find the most recent valid commit when the current segments
> file reports corruption. The patch found at
> https://github.com/apache/jackrabbit-oak/compare/trunk...ieb:KeepLuceneCommits
> keeps 10 previous commits.
> A more sophisticated policy could be used to save commits non-linearly over
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
