[
https://issues.apache.org/jira/browse/OAK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235485#comment-13235485
]
Michael Dürig commented on OAK-28:
----------------------------------
One thing we did not think of yet is access control: the jcr component needs to
pass information about the authenticated user down to the query API of oak-core
such that the query will only return items which the user is allowed to see.
> Query implementation
> --------------------
>
> Key: OAK-28
> URL: https://issues.apache.org/jira/browse/OAK-28
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, jcr
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Labels: query
> Attachments: OakToJcrQueryTreeConverter.java
>
>
> A query engine needs to be implemented.
> A query parser in oak-core should be able to handle xpath, sql2 and
> optionally other query languages. The jcr component must generate a valid
> query in one of those languages from JQOM queries and pass that statement
> along with value bindings, limit, offset, and name space mappings to the
> oak-core.
> We need to:
> * Define the oak-core API for handling queries. How are do we handle name
> space mappings, limit and offset
> * Implement a query builder in the jcr component which takes care of
> translating JQOM queries to statements in string form
> * Implement a query parser in oak-core and decide on a versatile AST
> representation which works with all query languages and which is extensible
> to future query languages.
> * Implement the actual query execution engine which interprets the query AST
--
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
