Description
We have a use case where the replication agent's enabled flag should not be overwritten with every deployment.
Referring to the comment here https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=16907459&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16907459 and the documentation for Property Filtering on https://jackrabbit.apache.org/filevault/filter.html , I am trying to implement this
<filter root="/etc/replication/agents.author/some-data-exporter"> <include pattern="/etc/replication/agents.author/some-data-exporter/.*"/> <exclude pattern=".*/enabled" matchProperties="true"/> </filter>
But when I deploy the package using this filter definition, the exclude pattern is not applied. Ideally this should include everything below the specified path and just ignore the property enabled in the existing content. But this is not happening as the whole content is replaced.
We are using this in AEM with the version 3.2.8(org.apache.jackrabbit.vault)
the Node structure is:
+/etc/replication/agents.author/some-data-exporter
+ jcr:content/
- enabled="true"
- property1="some value"
- property2="some other value"
Attachments
Issue Links
- is duplicated by
-
JCRVLT-519 Filter with explicit include/exclude definitions still overwrites existing properties
- Resolved
- is related to
-
JCRVLT-396 Import mode "MERGE" and "UPDATE" still may remove properties during import
- Closed
- relates to
-
JCRVLT-120 Allow to filter content properties based on property name and value
- Closed