jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OAK-5740) deliver overflow change even without new commit
Date Mon, 24 Jul 2017 13:17:06 GMT

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

Davide Giannella closed OAK-5740.
---------------------------------

Bulk close for 1.7.4

> 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
>              Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6
>             Fix For: 1.8, 1.7.4
>
>         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
(v6.4.14#64029)

Mime
View raw message