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

[jira] [Resolved] (OAK-1894) PropertyIndex only considers the cost of a single indexed property

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

Thomas Mueller resolved OAK-1894.
---------------------------------

    Resolution: Fixed

> PropertyIndex only considers the cost of a single indexed property
> ------------------------------------------------------------------
>
>                 Key: OAK-1894
>                 URL: https://issues.apache.org/jira/browse/OAK-1894
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>            Reporter: Justin Edelson
>            Assignee: Thomas Mueller
>             Fix For: 1.1, 1.0.2
>
>         Attachments: OAK-1894-advanced.patch, OAK-1894-old.patch, OAK-1894.patch
>
>
> The existing PropertyIndex loops through the PropertyRestriction objects in the Filter and essentially only calculates the cost of the first indexed property. This isn't actually the first property in the query and Filter.propertyRestrictions is a HashMap.
> More confusingly, the plan for a query with multiple indexed properties outputs *all* indexed properties, even though only the first one is used.
> For queries with multiple indexed properties, the cheapest property index should be used in all three relevant places: when calculating the cost, when executing the query, and when producing the plan.



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