[
https://issues.apache.org/jira/browse/OAK-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-1449:
---------------------------
Fix Version/s: (was: 1.1)
1.1.1
> 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.1.1
>
>
> 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.3.4#6332)
