[
https://issues.apache.org/jira/browse/OAK-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490543#comment-13490543
]
Jukka Zitting commented on OAK-388:
-----------------------------------
bq. an index is free to ignore that
Yes, that's a valid alternative. My point is that if we in any case need to do
the work of evaluating type inheritance at least in one index implementation,
it would be better to do it just once in the QueryEngine - both in terms of
performance and of avoiding duplicate code.
Note that the node type resolution is probably in any case needed (it's
currently not done since the cost estimates are so basic) for an index
implementation that understands node types to be able to give a reasonable cost
estimate, so the idea of avoiding type inheritance entirely for simple queries
like the one you mentioned.
bq. transforming the node type restriction into simple property constraints
+1 though as mentioned this will require extending the Filter mechanism with
support for OR clauses. I wonder if we should rather just replace Filter with a
Constraint from the abstract query tree.
> 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
