Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Fri, 4 May 2012 14:54:50 +0000 (UTC)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: 
 <280454727.27207.1336143290077.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2099323686.2915.1335535430428.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OAK-75) specify format and semantics of
 'filter' parameter in MicroKernel API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/OAK-75?page=3Dcom.atlassian.jir=
a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13268411=
#comment-13268411 ]=20

Michael D=C3=BCrig commented on OAK-75:
----------------------------------

bq. should we allow for node name filtering as well?
Would make sense since there are corresponding getNodes() call on the JCR A=
PI. Having to filter on top of the Microkernel might be very expensive for =
large node lists.=20

bq. if yes, do we need to specify separate filters for properties and node =
names?
I think it is sufficient to apply the filter to either of them. So we'd nee=
d a way to specify whether the filter should apply to the nodes or the prop=
erties.
               =20
> specify format and semantics of 'filter' parameter in MicroKernel API
> ---------------------------------------------------------------------
>
>                 Key: OAK-75
>                 URL: https://issues.apache.org/jira/browse/OAK-75
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: mk
>            Reporter: Stefan Guggisberg
>         Attachments: OAK-83.patch
>
>
> the following MicroKernel methods contain a 'filter' string parameter:
> - getJournal
> - diff
> - getNodes
> through the filter an API client could e.g. specify:
> - special 'meta' properties to be included (e.g. ":hash")
> - glob patterns on the names of properties/child nodes to be included/exc=
luded
> - path filter (for getJournal and diff)
> format/detailed semantics TBD, here's an initial proposal (json):
> {code}=20
> {
>   "path" : "/some/path",
>   "incl" : [ ":hash", "*" ],
>   "excl" : [ "tmp*" ]
> }
> {code}=20
> name filter patterns should ideally be the same=20
> format as specified for JCR Node.getNodes/getProperties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira