jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-233) Query should use the NodeStore abstraction
Date Thu, 09 Aug 2012 11:44:18 GMT

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

Jukka Zitting commented on OAK-233:
-----------------------------------

In revision 1371168 I added an extra {{NodeState}} argument to {{Query.executeQuery()}} for
this purpose. The method still also takes the MicroKernel revision identifier for compatibility
with existing index code.

As part of that revision and a proof of concept I modified the {{TraversingIndex}} implementation
to use the given {{NodeState}} instance instead of the MicroKernel revision. That allowed
me to also easily extend the implementation to support property restrictions instead of just
the path restrictions it had earlier.
                
> Query should use the NodeStore abstraction
> ------------------------------------------
>
>                 Key: OAK-233
>                 URL: https://issues.apache.org/jira/browse/OAK-233
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>
> Currently the query engine engine in oak-core uses the MicroKernel directly. It would
be better if it instead used the NodeStore/NodeState abstraction, as that would allow the
query code to leverage the existing JSON parsing, revision tracking and caching done in KernelNodeStore.

--
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

        

Mime
View raw message