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

Faster cost calculation for property indexes and traversal

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • property-index
    • None

    Description

      There are sometimes many property indexes, therefore cost calculation is slow. As seen in OAK-4076, we could re-order the indexes and stop once we found a good one (specially for unique indexes).

      Also, currently we still check if traversal is faster than using an index. In many cases this check is not needed.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. OAK-3480 Query engine: faster cost calculation (take 2)

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. OAK-2679 Query engine: faster cost calculation

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. OAK-4076 Benchmark to measure affect of number of indexes on uuid lookup performance

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. OAK-4904 For unique indexes avoid consulting indexes other than property index

          • Major - Major loss of function.
          • Closed

          Activity

            People

              thomasm Thomas Mueller
              thomasm Thomas Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: