jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1155) PropertyIndex cost calculation is faulty
Date Fri, 08 Nov 2013 11:55:17 GMT

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

Alex Parvulescu commented on OAK-1155:

added a workaround with rev [0].

I pushed the traversal fallback flag to the query, this allows for the distinction between
the defined query indexes and the traversal index. 
I think the traversal index should never be picked if there's a valid query index available
no matter the cost is provides, a property index is a subset of the entire repository, I can't
see a case where it's more efficient to traverse everything.

[0] http://svn.apache.org/r1539990

> PropertyIndex cost calculation is faulty
> ----------------------------------------
>                 Key: OAK-1155
>                 URL: https://issues.apache.org/jira/browse/OAK-1155
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, query
>            Reporter: Alex Parvulescu
>             Fix For: 0.11
> The cost calculation can easily go out of bounds when it needs to estimate (whenever
there are more than 100 nodes).
> The high value it returns can be higher than the traversal index which has a max of 10M,
but can be less smaller.
> For example:
>   100 nodes in the index:
>   with a single level /content cost is 6250000
>   adding a second level /content/data cost jumps to 1.544804416E9
>   101 nodes in the index:
>   with a single level /content cost is 100
>   adding a second level /content/data stays at 100
>   100 nodes, 12 levels deep, cost is 2.147483647E9
>   101 nodes, 12 levels deep, cost is 6.7108864E7

This message was sent by Atlassian JIRA

View raw message