[
https://issues.apache.org/jira/browse/OAK-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268411#comment-13268411
]
Michael Dürig 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 API.
Having to filter on top of the Microkernel might be very expensive for large
node lists.
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 need a
way to specify whether the filter should apply to the nodes or the properties.
> 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/excluded
> - path filter (for getJournal and diff)
> format/detailed semantics TBD, here's an initial proposal (json):
> {code}
> {
> "path" : "/some/path",
> "incl" : [ ":hash", "*" ],
> "excl" : [ "tmp*" ]
> }
> {code}
> name filter patterns should ideally be the same
> 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 administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
