Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6776

Correctly use IndexPlan.supportsPathRestrictions

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.12, 1.8.0
    • Component/s: query
    • Labels:
      None

      Description

      Right now, IndexPlan.supportsPathRestrictions (introduced in OAK-6734) is used in the query engine for some kind of mixed "rule based" and "cost based" query optimization.

      I think the current implementation isn't correct, as (for example) a query with multiple indexes will now use the wrong index in some cases (for example property index, even if the cost of the Lucene index is lower).

      Also, if there is a Lucene index with supportsPathRestrictions, and one without, right now always the one with supportsPathRestrictions is used. This is probably better right now, but once OAK-6735 is resolved, this should be fixed as well.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                thomasm Thomas Mueller
                Reporter:
                thomasm Thomas Mueller
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: