Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-2005 Use separate Lucene index for performing property related queries
  3. OAK-2200

Tune cost calculation for lucene property index

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.0.8, 1.1.2
    • lucene
    • None

    Description

      Though lucene provides an accurate count with IndexReader#numDocs, we may need to apply heuristics to constrain the value so that it is properly selected for indexed properties Vs other inappropriate indexes e.g wrt nodeType index.

      Attachments

        1. OAK-2200.patch
          7 kB
          Amit Jain

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. OAK-6333 IndexPlanner should use actual entryCount instead of limiting it to 1000

          • Major - Major loss of function.
          • Closed

          Activity

            People

              amitjain Amit Jain
              amitjain Amit Jain
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: