[
https://issues.apache.org/jira/browse/OAK-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269483#comment-13269483
]
Michael Dürig commented on OAK-75:
----------------------------------
Regarding the filter syntax: couldn't we make it a bit more lightweight and
general? For example
{code}
{
nodes: [ "foo\*", "\-foo1" ],
properties: [ "bar\*", "tmp" ]
}
{code}
would only include nodes whose names start with "foo" and whose name is not
"foo1" and all properties whose name start with "bar" or whose name is "tmp".
> 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
