jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-388) Add NodeType Index
Date Mon, 05 Nov 2012 09:51:12 GMT

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

Marcel Reutegger commented on OAK-388:

I don't think we need to make all index implementation aware of node type constraints. Of
course they know there's a node type constraint because the Filter exposes it, but a filter
is free to ignore that and only handle one particular restriction of a Filter. IIUC the query
engine will pick the best index based on the cost. This may mean an index that resolves a
node type constraint may not be used at all. E.g. if we extend your example above like this:
{{SELECT * FROM [mix:referenceable] where [jcr:uuid] = 'xxxx'}}, the query engine better not
resolves the node type through an index, but rather use the property index for jcr:uuid only.
This should be possible based on the cost.

On the other hand I was also thinking about transforming the node type restriction into simple
property constraints last week. This would also remove the rather JCR specific node type restriction
from Filter.
> Add NodeType Index
> ------------------
>                 Key: OAK-388
>                 URL: https://issues.apache.org/jira/browse/OAK-388
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Alex Parvulescu
>            Assignee: Marcel Reutegger
>             Fix For: 0.6
>         Attachments: oak-core-property-index.patch
> I'm proposing a new property index for node types.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message