jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-5740) deliver overflow change even without new commit
Date Wed, 19 Jul 2017 07:50:00 GMT

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

Stefan Egli resolved OAK-5740.
    Resolution: Fixed

Agreed, I've committed the patch in http://svn.apache.org/viewvc?rev=1802360&view=rev

Let's wait with looking into backporting until this has been tested in trunk for a few weeks.

> 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
>            Assignee: Stefan Egli
>            Priority: Minor
>             Fix For: 1.8
>         Attachments: OAK-5740.StuffAtop-v2-patch.patch, OAK-5740.testcase.patch, OAK-5740.testcase.patch,
OAK-5740.v2.patch, OAK-5740.v3.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

View raw message