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 2018/11/01 11:26:02 UTC

[jira] [Updated] (OAK-7074) Ensure that all Documents are read with document order traversal indexing

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

Davide Giannella updated OAK-7074:
----------------------------------
    Fix Version/s: 1.9.11

> Ensure that all Documents are read with document order traversal indexing
> -------------------------------------------------------------------------
>
>                 Key: OAK-7074
>                 URL: https://issues.apache.org/jira/browse/OAK-7074
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk, run
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Major
>             Fix For: 1.10, 1.9.10, 1.9.11
>
>
> With OAK-6353 support was added for document order traversal indexing. In this mode we open a DB cursor and try to read all documents from it using document order traversal. Such a cursor may remain open for long time (2-4 hrs) and its possible that document may get reordered by the Mongo storage engine. This would result in 2 aspects to be thought about 
> # Duplicate documents - Same document may appear more than once in result set 
> # Possibly missed document - It may be a possibility that a document got moved and missed becoming part of cursor. 
> Both these aspects would need to be handled



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