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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/02/19 17:04:18 UTC

[jira] [Closed] (OAK-4009) Search done via Lucene index might return duplicate results

     [ https://issues.apache.org/jira/browse/OAK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella closed OAK-4009.
---------------------------------

Bulk close for 1.3.16

> Search done via Lucene index might return duplicate results
> -----------------------------------------------------------
>
>                 Key: OAK-4009
>                 URL: https://issues.apache.org/jira/browse/OAK-4009
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.3.0
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Blocker
>             Fix For: 1.3.16
>
>         Attachments: OAK-4009-v1.patch
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)