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 "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2017/02/08 09:42:41 UTC
[jira] [Updated] (OAK-5556) Allow filter paths for Check command
[ https://issues.apache.org/jira/browse/OAK-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu updated OAK-5556:
---------------------------------
Description:
It would be good if the {{check}} command would allow for filtering on content path. This would help in quickly identifying what is the good revision of a specific broken node in cases of very large repos.
This feature could go hand in hand with refactoring {{ConsistencyChecker}} in order to better distinguish when:
* a full path at the given revision is checked
* a node and its properties are checked
* a node and its descendants are checked
was:It would be good if the {{check}} command would allow for filtering on content path. This would help in quickly identifying what is the good revision of a specific broken node in cases of very large repos.
> Allow filter paths for Check command
> ------------------------------------
>
> Key: OAK-5556
> URL: https://issues.apache.org/jira/browse/OAK-5556
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar, segmentmk
> Reporter: Alex Parvulescu
> Assignee: Andrei Dulceanu
> Labels: tooling
> Fix For: 1.8
>
>
> It would be good if the {{check}} command would allow for filtering on content path. This would help in quickly identifying what is the good revision of a specific broken node in cases of very large repos.
> This feature could go hand in hand with refactoring {{ConsistencyChecker}} in order to better distinguish when:
> * a full path at the given revision is checked
> * a node and its properties are checked
> * a node and its descendants are checked
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)