[
https://issues.apache.org/jira/browse/OAK-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040640#comment-14040640
]
Thomas Mueller commented on OAK-1902:
-------------------------------------
The patch is a bit too large for me to fully review right now.
[~justinedelson], is it still an issue if /oak:index/nodetype/entryCount is set
to a very high value, for example 9223372036854776000?
> NodeTypeIndex is not conversative enough about its cost
> -------------------------------------------------------
>
> Key: OAK-1902
> URL: https://issues.apache.org/jira/browse/OAK-1902
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Reporter: Justin Edelson
> Fix For: 1.0.2
>
> Attachments: OAK-1902.patch
>
>
> NodeTypeIndexProvider derives its cost from PropertyIndexLookup.
> PropertyIndexLookup has a hardcoded maximum cost (which actually isn't a
> maximum cost, but is more the maximum number of nodes which will be read
> during cost calcuation).
> IMHO, these maximum costs should not be the same. In my experience with
> JCR-based applications, the number of matches for a particular node type is
> far greater than the number of matches for a regular property value.
> As a result, I would suggest that if the maximum cost is reached, a greater
> penalty should be applied to a node type index than a regular property index.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
