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

Search done via Lucene index might return duplicate results

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.2.14, 1.3.16, 1.4
    • Component/s: lucene
    • Labels:
      None

      Description

      In certain cases (like one explained in OAK-2569) it can happen that Lucene index version gets updated in between a cursor traversal. Then the offset used would be wrong and currently the LucenePropertyIndex would run the query without offset which can result in duplicate rows.

      As that time we relied on seenPaths for ensuring that duplicate paths would be detected. However a closer look at code flow now indicates that it gets used only for those queries where we do path transformation [1] and not in all cases.

      Also earlier we did used unique cursor but we changed that in OAK-2754 in favour of seenPaths. So as a fix we should revert that back and use unique cursor there

      [1] search on jcr:conent/@title and actual search done for 'title' and path checked to end with jcr:content

        Attachments

        1. OAK-4009-v1.patch
          6 kB
          Chetan Mehrotra

          Issue Links

            Activity

              People

              • Assignee:
                chetanm Chetan Mehrotra
                Reporter:
                chetanm Chetan Mehrotra
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: