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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2017/02/21 11:24:44 UTC

[jira] [Comment Edited] (OAK-5740) deliver overflow change even without new commit

    [ https://issues.apache.org/jira/browse/OAK-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875820#comment-15875820 ] 

Stefan Egli edited comment on OAK-5740 at 2/21/17 11:24 AM:
------------------------------------------------------------

Attaching [^OAK-5740.testcase.patch] (2nd version is the one which actually fails) which contains a suggested test case. [~catholicon], wdyt?


was (Author: egli):
Attaching [^OAK-5740.testcase.patch] which contains a suggested test case. [~catholicon], wdyt?

> deliver overflow change even without new commit
> -----------------------------------------------
>
>                 Key: OAK-5740
>                 URL: https://issues.apache.org/jira/browse/OAK-5740
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 1.6.0
>            Reporter: Stefan Egli
>            Priority: Minor
>         Attachments: OAK-5740.testcase.patch, OAK-5740.testcase.patch
>
>
> As [reported|http://markmail.org/message/2qxle24f6zu2vpms] by [~catholicon] on oak-dev the observation queue only delivers the so-called _overflow entry/change_ only when new commits are 'coming in'. We might want to consider fixing this, even though arguably this is a very rare case (since typically the observation queue is configured to be very large)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)