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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/05/08 11:36:04 UTC
[jira] [Resolved] (OAK-6181) MongoMissingLastRevSeeker may return
incomplete candidate set
[ https://issues.apache.org/jira/browse/OAK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-6181.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
The implementation now does a query with an order by ascending on _modified. This ensures a concurrently updated document always moves in front of the cursor.
Fixed in trunk: http://svn.apache.org/r1794332
> MongoMissingLastRevSeeker may return incomplete candidate set
> -------------------------------------------------------------
>
> Key: OAK-6181
> URL: https://issues.apache.org/jira/browse/OAK-6181
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 1.0, 1.2, 1.4, 1.6.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.7.0, 1.8
>
>
> The set returned by {{MongoMissingLastRevSeeker.getCandidates()}} may be incomplete. See also discussion in OAK-4535 and on [oak-dev|https://lists.apache.org/thread.html/36ade745b7f6a0417aab578c21ca9fb072a7d6e5c43c724b85a153bf@%3Coak-dev.jackrabbit.apache.org%3E].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)