You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by "Thomas Mueller (Commented) (JIRA)" <ji...@apache.org> on 2012/04/03 10:58:44 UTC

[jira] [Commented] (OAK-34) Define query API

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

Thomas Mueller commented on OAK-34:
-----------------------------------

I have committed a first prototype. Some parts are still missing (for example offset and limit), and the CoreValue is still in the package org.apache.jackrabbit.oak.query. But I would like to get feedback first on the query part itself. Is it OK if the Result and ResultRow interfaces are in the package org.apache.jackrabbit.oak.api? Is the interface QueryEngine required, it should the two methods be moved to Connection? Are the interface and method names OK?
                
> Define query API
> ----------------
>
>                 Key: OAK-34
>                 URL: https://issues.apache.org/jira/browse/OAK-34
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core
>            Reporter: Michael Dürig
>              Labels: query
>
> Define a oak-core API for handling queries. How do we handle name space mappings, value bindings, limit, offset, access rights. See OAK-28

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