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 2019/03/28 13:11:06 UTC

[jira] [Updated] (OAK-8046) Result items are not always correctly counted against the configured read limit if a query uses a lucene index

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

Davide Giannella updated OAK-8046:
----------------------------------
    Fix Version/s:     (was: 1.11.0)

> Result items are not always correctly counted against the configured read limit if a query uses a lucene index 
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-8046
>                 URL: https://issues.apache.org/jira/browse/OAK-8046
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>    Affects Versions: 1.8.7
>            Reporter: Georg Henzler
>            Assignee: Vikas Saurabh
>            Priority: Major
>             Fix For: 1.12.0, 1.10.1, 1.8.12
>
>         Attachments: OAK-8046-take2.patch, OAK-8046.patch
>
>
> There are cases where an index is re-opened during query execution. In that case, already returned entries are read again and skipped, so basically counted twice. This should be fixed to only count entries once (see also [1])
> The issue most likely exists since the read limit was introduced with OAK-6875
> [1] https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)