[
https://issues.apache.org/jira/browse/OAK-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091828#comment-16091828
]
Vikas Saurabh commented on OAK-5740:
------------------------------------
[~egli], I could not read through the patch closely (but, I had seen the
changes earlier anyway.. so, "patch lgtm" still holds :) ).
I think we should fix this issue (... and if that sounds too risky to others,
then close this issue noting the same)... I mean that I don't see any point in
holding this issue open.
> 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
(v6.4.14#64029)
