[jira] [Commented] (JCRVLT-120) Allow to filter content properties based on property name and value

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus commented on JCRVLT-120:
----------------------------------------

I am currently preparing a patch for the documentation in https://jackrabbit.apache.org/filevault/filter.html for this feature. The desired behaviour for the import is not quite clear for me when property filtering is being used though. Should excluded properties below covered nodes of a package
a) not be touched in the repository
b) be removed

According to https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=15396063&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15396063 it seems to be b) which is quite confusing because in fact excluded nodes (with no package filtering) are rather following the approach a).

Also the description says "based on property name and value" but I only see filtering being supported based on property name (not on the value).
[~tripod] or [~marett] Can you guys clarify?

> 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
>            Priority: Major
>             Fix For: 3.1.28
>
>         Attachments: JCRVLT-120.patch, JCRVLT-120.patch, JCRVLT-120.patch
>
>
> 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
(v7.6.14#76016)