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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2017/02/28 13:18:45 UTC

[jira] [Commented] (OAK-5862) Consistency check outputs wrong number of binary properties in debug messages

    [ https://issues.apache.org/jira/browse/OAK-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887982#comment-15887982 ] 

Michael Dürig commented on OAK-5862:
------------------------------------

+1, makes sense. 

> Consistency check outputs wrong number of binary properties in debug messages
> -----------------------------------------------------------------------------
>
>                 Key: OAK-5862
>                 URL: https://issues.apache.org/jira/browse/OAK-5862
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: run, segment-tar
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>             Fix For: 1.7.0, 1.8
>
>         Attachments: OAK-5862.patch
>
>
> {{check . --filter /a --notify 0}}
> Running above command for a node {{/a}} with 5 blob properties produces the following output:
> {code}
> Checking /a
> Traversing /a
> Checking /a/a0 = {2000 bytes}
> Checking /a/a1 = {2000 bytes}
> Checking /a/a2 = {2000 bytes}
> Checking /a/a3 = {2000 bytes}
> Checking /a/a4 = {2000 bytes}
> Checked 1 nodes and 0 properties
> {code}
> Although binary properties are not checked, wrong debug messages are being produced. Debug messages should match the final tally of properties checked which is correct.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)