[
https://issues.apache.org/jira/browse/OAK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-4009:
---------------------------------
Attachment: OAK-4009-v1.patch
[patch for the same|^OAK-4009-v1.patch] As suggestion and spellcheck use same
path for all result rows we cannot enable unique cursor for all cases
[~catholicon] Can you have a look
[~teofili] For Facets I am not sure how is the path - Is it unique? Otherwise
would need to identify that we are dealing with a facet query and use a non
unique cursor
> 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
> 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)
