[
https://issues.apache.org/jira/browse/JCRVLT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395963#comment-15395963
]
Tobias Bocanegra commented on JCRVLT-120:
-----------------------------------------
- is the requirement to exclude those properties from the package, or to ignore
them when installing?
- if they are excluded, should they be retained/merged with existing ones when
installed?
I think that basic filtering should be handled by the workspace filter. this
would better align with the roadmap, where we eventually simplify aggregation
and go away from the jcr-vlt commandline support.
we could extend the workspace to support properties. either implicitly by path
or explicitly through special notation. eg:
{noformat}
<workspaceFilter version="1.0">
<filter root="/content">
<exclude pattern=".*/cq:lastReplicated" />
</filter>
</workspaceFilter>
{noformat}
or better explicit to remain backward compatible:
{noformat}
<workspaceFilter version="1.0">
<filter root="/content">
<exclude pattern=".*/@cq:lastReplicated" />
</filter>
</workspaceFilter>
{noformat}
or
{noformat}
<workspaceFilter version="1.0">
<filter root="/content">
<exclude pattern=".*/cq:lastReplicated" matchProperties="true" />
</filter>
</workspaceFilter>
{noformat}
> Allow to filter content properties based on property name and value
> --------------------------------------------------------------------
>
> Key: JCRVLT-120
> URL: https://issues.apache.org/jira/browse/JCRVLT-120
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Affects Versions: 3.1.26
> Reporter: Timothee Maret
>
> In our use case, we need to filter content distributed by filevault for
> properties {{cq:lastReplicated}}, {{cq:lastReplicatedBy}} and
> {{cq:lastReplicationAction}}.
> This feature could cover more than those three property and instead be
> generalised to filter any property which name and value match the configured
> filter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
