jackrabbit-oak-issues 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-388) Add NodeType Index
Date Mon, 05 Nov 2012 09:29:12 GMT

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

Jukka Zitting commented on OAK-388:

Note that instead of making all index implementations interpret node type constraints directly,
it would IMHO be better if the QueryEngine took care of turning node type constraints (including
explicit property constraints on {{jcr:primaryType}} or {{jcr:mixingType}}) into sets of property

For example, a {{SELECT * FROM [mix:referenceable]}} query could result in a constraint like
{{([jcr:primaryType] IN (<list of referenceable primary types>) OR ([jcr:mixinTypes]
IN (<list of referenceable mixin types)}}. Of course doing that would require extending
the current Filter mechanism to support OR clauses or IN constraints. Alternatively we could
just preprocess the original abstract query tree and pass it directly down to the index implementations
instead of mapping the constraints first to a 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