[
https://issues.apache.org/jira/browse/OAK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235438#comment-13235438
]
Marcel Reutegger commented on OAK-28:
-------------------------------------
Regarding value bindings and query parsing in the jcr binding: I don't think we
can avoid parsing and at the same time use literals instead of value bindings.
IMO the latter requires that you parse the query in order to find out what and
where the bind variable names are. Therefore I'd rather not parse the query
statement in the jcr binding and pass the map of bind variables/values.
> 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 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 size
> * Implement a query builder in the jcr component which takes care of
> translating JQOM queries
> * 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
