joerghoh commented on code in PR #414:
URL:
https://github.com/apache/jackrabbit-filevault/pull/414#discussion_r2783918943
##########
vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/Importer.java:
##########
@@ -1036,8 +1039,132 @@ private void commit(Session session, TxInfo info,
LinkedList<TxInfo> skipList)
}
}
+ /**
+ * Restores the coverage filter on the artifact set from the aggregator
configuration.
+ * This is necessary because the coverage filter metadata is lost during
the archive→import flow.
+ *
+ * The coverage filter determines which child nodes are "covered" by this
aggregate and should
+ * be removed if not present in the package. Aggregators with partial
coverage (e.g., folder
+ * aggregates with {@code <exclude isNode="true" />}) should preserve
child nodes that are
+ * outside their coverage.
+ *
+ * This method only applies the filter when there are child aggregates
(hints), which indicates
Review Comment:
I provided the test case in JCRVLT-830, and aggregation (or its
consequences) indeed influence the import.
[Importer.commit()](https://github.com/apache/jackrabbit-filevault/blob/3d74b96d4cf6d953302335c9faacc7e1b09ab595/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/Importer.java#L1039)
is structured around the different types of artifacts (aggregations).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
