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 2017/09/27 13:36:00 UTC

[jira] [Created] (OAK-6734) IndexPlan: add supportsPathRestrictions

Thomas Mueller created OAK-6734:
-----------------------------------

             Summary: IndexPlan: add supportsPathRestrictions
                 Key: OAK-6734
                 URL: https://issues.apache.org/jira/browse/OAK-6734
             Project: Jackrabbit Oak
          Issue Type: Improvement
            Reporter: Thomas Mueller
             Fix For: 1.8


Some indexes support path restrictions (for example Lucene indexes, if configured to do so). For such cases, the cost of using the index is at most the cost of traversing.

There are two ways to solve this: (1) the index itself could (somehow) ask the counter index about the estimated number of nodes for that path. (2) the query engine can do that itself, so that the index doesn't need to implement this logic.

Let's do approach (2), and add a method supportsPathRestrictions to the IndexPlan interface. If it returns false (default), the behavior is the same as right now. If it returns true, then the cost of the index is adjusted to the estimated number of nodes in this path.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)