You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/06/23 13:22:24 UTC

[jira] [Assigned] (OAK-1902) NodeTypeIndex is not conversative enough about its cost

     [ https://issues.apache.org/jira/browse/OAK-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller reassigned OAK-1902:
-----------------------------------

    Assignee: Thomas Mueller

> 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
>            Assignee: Thomas Mueller
>             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)