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

Andrei Dulceanu edited comment on OAK-5276 at 2/9/17 10:19 AM:
---------------------------------------------------------------

Committed a slightly modified version of the initial patch in trunk at 
r1781379. Fixed an inconsistency in the code which prevented the new 
{{--notify}} option to accept  {{0}} as argument, in order to log all the 
progress of the traversal. Also included the documentation update.

[~frm], thanks for reviewing!


was (Author: dulceanu):
Committed a slightly modified version of the initial patch at r1781379. Fixed 
an inconsistency in the code which prevented the new {{--notify}} option to 
accept  {{0}} as argument, in order to log all the progress of the traversal. 
Also included the documentation update.

[~frm], thanks for reviewing!

> The check command overloads the meaning of the "deep" option
> ------------------------------------------------------------
>
>                 Key: OAK-5276
>                 URL: https://issues.apache.org/jira/browse/OAK-5276
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run, segment-tar
>            Reporter: Francesco Mari
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>              Labels: tooling
>             Fix For: 1.7.0, 1.8, 1.6.1
>
>         Attachments: OAK-5276.patch
>
>
> The {{--deep}} option accepted by the {{check}} command is semantically 
> overloaded. It is used both as a flag to enable deep content traversal and as 
> a way to specify the frequency of debug messages printed by the tool. 
> This option should be split in two. In particular, {{--deep}} should retain 
> its behaviour of on/off flag for deep traversal, and a new command line 
> option should be introduced to specify the interval of debug messages.



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

Reply via email to