[
https://issues.apache.org/jira/browse/OAK-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882846#comment-13882846
]
Michael Dürig commented on OAK-1332:
------------------------------------
bq. Both needs could be addressed by (lazily) tracking the current path and
identifier while recursing down the content diff,
This is means either keeping a reference to the respective content diff, which
would however also keep the references to the involved before and after states.
Or introducing a dedicated class for tracking those paths and identifiers,
effectively a slimmed down version of {{ImmutableTree}}.
bq. Once it reaches some predefined limit, it would stop the diff and add a
continuation that would redo the diff, skip the changes already seen,
Nice idea. But I'd rather postpone this until we have a case for it. So far the
impact of the events lingering around because the client (e.g. Sling) keeps a
reference to it seems to be much greater than that from events queued
internally by Oak.
> Large number of changes to the same node can fill observation queue
> -------------------------------------------------------------------
>
> Key: OAK-1332
> URL: https://issues.apache.org/jira/browse/OAK-1332
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Minor
> Fix For: 0.16
>
>
> Changing, adding or removing a lot of (10'000s or more) direct children of
> node with on save() might cause observation queues to fill up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
