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:30:25 UTC

[jira] [Commented] (OAK-1903) PropertyIndex applies 10x penalty to is not null queries even when the node count is known

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

Thomas Mueller commented on OAK-1903:
-------------------------------------

I think it should be "if (count >= max) {" instead of "if (count > max) {".

> PropertyIndex applies 10x penalty to is not null queries even when the node count is known
> ------------------------------------------------------------------------------------------
>
>                 Key: OAK-1903
>                 URL: https://issues.apache.org/jira/browse/OAK-1903
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.0, 1.0.1
>            Reporter: Justin Edelson
>            Assignee: Thomas Mueller
>             Fix For: 1.0.2
>
>         Attachments: OAK-1903.patch
>
>
> ContentMirrorStoreStrategy has a bit of code which multiples the cost of a "is not null" query by 10. This code was added in r1501746, but there's nothing in the related JIRA (OAK-894) which mentions this change.
> It appears to me that this multiplier should only take effect *if* the maximum node count has been reached. Otherwise, this code vastly overstates the cost of a query.
> In a recent test, a property on 45 nodes generated a cost of 452.



--
This message was sent by Atlassian JIRA
(v6.2#6252)