[
https://issues.apache.org/jira/browse/OAK-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875975#comment-15875975
]
Vikas Saurabh commented on OAK-5740:
------------------------------------
The test case looks ok to me to show the point of the issue. That said, I'm
still of the opinion that if this is observed only special case (e.g.
controlled test case), then may be some util class/method (exposed?? in case
some external observer want it!) would be ok. Of course, with the documented
behavior.
bq. the observation queue is configured to be very large
I think the actual reason is that there are always commits that happen - update
of ":async" node for example... may be even topology (although I don't know if
that's true even in single-node-tar-setups too).
> 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)
