[
https://issues.apache.org/jira/browse/OAK-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu updated OAK-5753:
---------------------------------
Attachment: OAK-5753-02.patch
As discussed, I added also the revision date to the summary log messages. Now a
message looks like this:
{code}
Latest good revision for path /f is eb7b9b64-db84-4752-adf5-212e3e651c1c:59
from Feb 28, 2017 12:01:33 PM
{code}
[~mduerig], could you take another look at the latest patch, please?
> Consistency check incorrectly fails for broken partial paths
> -------------------------------------------------------------
>
> Key: OAK-5753
> URL: https://issues.apache.org/jira/browse/OAK-5753
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: run, segment-tar
> Affects Versions: 1.8
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Labels: tooling
> Fix For: 1.7.0, 1.8
>
> Attachments: OAK-5753-02.patch, OAK-5753.patch
>
>
> To better explain the bug I'll describe the content of the revisions:
> # Valid Revision
> Adds child nodes {{a}}, {{b}}, {{c}}, {{d}}, {{e}}, {{f}} with various
> properties (blobs included)
> # Invalid Revision
> Adds child node {{z}} with some blob properties and then corrupts the
> {{NODE}} record holding {{z}}.
> Now when the consistency check is run, it correctly detects that the second
> revision is broken, *marks the path {{/z}} as corrupt* and then continues
> checking the first valid revision. Because of a check introduced for OAK-5556
> [1], which tries to validate the user provided absolute paths before checking
> them, the checker tries to check {{/z}} in the first revision, where of
> course it can't find it. Therefore the check incorrectly fails for this
> revision, although it shouldn't have to.
> /cc [~mduerig], [~frm]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
