[
https://issues.apache.org/jira/browse/OAK-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296527#comment-16296527
]
Vikas Saurabh commented on OAK-7074:
------------------------------------
Also, in the same offline discussion - for problem#2 in description (document
_may_ not show up at all), it seemed that we could also run another query with
_modified > checkpointTime. Since we're now removing the dups - this should
still be ok. (note, a document might move because of a reverted commit - so, we
must have all the documents that existed at checkpoint).
The question about some document getting missed due to mongo internal process
is, imo, would require some more guarantees from mongo (as [~chetanm] indicated
in #2 in his last comment).
> 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
> Fix For: 1.8
>
>
> 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
(v6.4.14#64029)
