You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2018/11/29 14:05:00 UTC

[jira] [Resolved] (OAK-7918) Extract checking logic from ConsistencyChecker

     [ https://issues.apache.org/jira/browse/OAK-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Mari resolved OAK-7918.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.13

Resolving this issue. The changes made so far are enough to go on with OAK-7866. Further improvements will be tracked by additional issues.

> Extract checking logic from ConsistencyChecker 
> -----------------------------------------------
>
>                 Key: OAK-7918
>                 URL: https://issues.apache.org/jira/browse/OAK-7918
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>            Priority: Major
>             Fix For: 1.10, 1.9.13
>
>         Attachments: OAK-7918-01.patch, OAK-7918-02.patch, OAK-7918-03.patch, OAK-7918-04.patch
>
>
> {{ConsistencyChecker}} mixes both the logic proper to a consistency check and reporting and debug statements. Moreover, it is not possible to retrieve programmatically the result of a consistency check, making it impossible to reuse this class in another context. The logic for a consistency check should be extracted to separate class.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)