[jira] [Resolved] (OAK-1035) Property Index: cost calculation is wrong (zero) when searching for many values

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller resolved OAK-1035.
---------------------------------

    Resolution: Fixed

Revision 1525573 (fix and test case)
                
> Property Index: cost calculation is wrong (zero) when searching for many values
> -------------------------------------------------------------------------------
>
>                 Key: OAK-1035
>                 URL: https://issues.apache.org/jira/browse/OAK-1035
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>
> Currently, for queries of the form 
> {code}
> select * from [nt:unstructured] where type = 'xyz'
> {code}
> the node type index is used in some cases, even if there is an index on the property "type". The reason is that the cost for the node type index is 0 due to a bug. The node type index internally uses the property index on the property "jcr:primaryType", and asks for the cost using all possible children node types of "nt:unstructured". The returned cost is 0 because of this bug. The cost estimation is an extrapolation of the number of entries for the first 3 values. It is currently coded as:
> {code}
> count = count / size / i;
> {code}
> when in fact it should be written as:
> {code}
> count = count * size / i;
> {code}

--
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