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

Konrad Windszus edited comment on JCRVLT-787 at 11/27/24 3:38 PM:
------------------------------------------------------------------

[~joerghoh] Is this related to JCRVLT-755? Where do you expect those metrics to 
be emitted. At the end of the installation log?

There is already the number of modified nodes emitted in 
https://github.com/apache/jackrabbit-filevault/blob/72adfdd907a1056381aa29695f57505293b39f46/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/AutoSave.java#L166.


was (Author: kwin):
[~joerghoh] Is this related to JCRVLT-755? Where do you expect those metrics to 
be emitted. At the end of the installation log?

> 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)

Reply via email to