[
https://issues.apache.org/jira/browse/OAK-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303818#comment-15303818
]
Julian Sedding commented on OAK-4402:
-------------------------------------
Not sure about this. Since the removal happens without any of the JCR commit
hooks, using such a command could easily lead to repository corruption (e.g.
removal of referenced nodes/versions -> referential integrity violation,
removal of mandatory children -> nodetype constraint violation).
That said, these operations are already possible today, just not as easy.
[~akhoury] what is the use-case/motivation for this feature? Why can the same
not be achieved via the JCR API?
> 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)
