jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-75) specify format and semantics of 'filter' parameter in MicroKernel API
Date Mon, 30 Apr 2012 08:45:44 GMT

    [ https://issues.apache.org/jira/browse/OAK-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264737#comment-13264737

Thomas Mueller commented on OAK-75:

About "path": for many methods, the path is a parameter (commit, getChildNodeCount, getNodes,
nodeExists). For others methods, I guess it will be specified in the filter (diff, getJournal).
For the one getNodes method, the path is a parameter and could be set in the filter as well.
Could that lead to confusion?

I noticed getJournal supports a filter, but the related getRevisionHistory not yet. Would
it make sense to add the filter to getRevisionHistory as well?

If we support path filtering in getJournal (I hope we do), should we support it in waitForCommit
and getHeadRevision as well?
> 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
> 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


View raw message