[
https://issues.apache.org/jira/browse/JCRVLT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951224#comment-17951224
]
Joerg Hoh commented on JCRVLT-787:
----------------------------------
[~reschke] I agree on the granularity of the JCR call, and that the API does
not deliver any additional information how much nodes were deleted.
Oak has a functionality which allows to efficiently query an approximate number
of nodes in that subtree (exposed via the NodeCounter mbean). Having such an
approximate number would be sufficient in this case.
> package installation should provide metrics
> -------------------------------------------
>
> Key: JCRVLT-787
> URL: https://issues.apache.org/jira/browse/JCRVLT-787
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.8.2
> Reporter: Joerg Hoh
> Priority: Major
>
> We recently had an issue that the installation of a content package caused
> the deletion of a large content subtree; while the package worked as it
> should , installing the package was neither expected nor known.
> For that reason we just saw the result and it took a while to identify the
> package installation as the root-cause of this situation. This was
> complicated by the lack of know-how and familiarity of the investigating
> people with filevault and content packages.
> For that reason it would be great if filevault could provide a collection of
> metrics (nodes added, nodes deleted, etc) when a package has been
> successfully installed.
> In this case the situation was like this: The filter.xml contained a rule for
> /content/foobar with no mode specified (so the default value of REPLACE was
> used), and in the package just a .content.xml for /content/foobar was
> included; that wiped the entire subtree (a few thousand nodes) in the
> repository below /content/foobar.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
