[
https://issues.apache.org/jira/browse/OAK-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304275#comment-15304275
]
Andrew Khoury commented on OAK-4402:
------------------------------------
Hi [~jsedding], the main motivation is for dealing with emergency situations
where there is some corruption or issue with the repository and we are ok just
deleting the problematic nodes.
I have used a script provided by [~alex.parvulescu] in the past to do the same
thing: https://gist.github.com/stillalex/43c49af065e3dd1fd5bf
We used this to remove nodes to fix the following issues:
1. Remove corrupt or large property indexes while the application using Oak is
stopped
2. Remove corrupt nodes (Mongo revision error and Tar SegmentNotFoundException)
3. Remove protected nodes like corrupt version histories
> Add rm command to the oak-run console tool
> ------------------------------------------
>
> Key: OAK-4402
> URL: https://issues.apache.org/jira/browse/OAK-4402
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Affects Versions: 1.0.30, 1.4.2, 1.2.15
> Reporter: Andrew Khoury
> Priority: Minor
>
> It would be great if the oak-run console provided an rm command. I
> implemented the command against oak 1.0.x branch long ago and submitted a
> pull request in the github repo.
> Here's the pull request:
> https://github.com/apache/jackrabbit-oak/pull/24
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
