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 "angela (JIRA)" <ji...@apache.org> on 2014/02/26 20:03:22 UTC

[jira] [Commented] (OAK-1449) Troubleshooting tool to inspect hidden items

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

angela commented on OAK-1449:
-----------------------------

the permission store is not hidden.

IMO there is nothing specific we have to add here. any tool that allows to operate directly on the NodeStore will be able to access items irrespective if they are hidden on the oak api.

> Troubleshooting tool to inspect hidden items
> --------------------------------------------
>
>                 Key: OAK-1449
>                 URL: https://issues.apache.org/jira/browse/OAK-1449
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Marth
>            Priority: Minor
>              Labels: production, resilience, tools
>             Fix For: 1.0
>
>
> For troubleshooting borked instances we should have a way to inspect (and write to?) the complete tree, including items that are hidden. Permission tree, version tree, indexes, etc come to mind.
> We need to design this tool in a way that does not compromise security, but on the other hand I think we need write capabilities in order to fix broken items if needed. Not sure, how to best do this...
> The tool ideally can be limited to look at
> * specific paths only and
> * ranges of MVCC revisions



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)