[
https://issues.apache.org/jira/browse/OAK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739627#comment-13739627
]
Jukka Zitting commented on OAK-659:
-----------------------------------
bq. I would expect the change in the index to be of the same order as the rest
of the change
The problem here is that we already have auto-purging for the changes made by
the client, but not for those triggered by commit hooks. So while the current
design achieves our big transaction goal with O(1) memory use, it only does so
if there are only O(1) changes from commit hooks. The motivation for this
change is thus to keep the O(1) memory limit even if a commit hook adds O(n)
changes to the commit (which an indexer would typically do).
> Move purge logic for transient changes below the NodeBuilder interface
> ----------------------------------------------------------------------
>
> Key: OAK-659
> URL: https://issues.apache.org/jira/browse/OAK-659
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Attachments: OAK-659-2.patch, OAK-659.patch
>
>
> Currently transient changes are purged down to a persisted branch once a
> certain size threshold is hit. This logic currently resides in {{RootImpl}}.
> However this approach doesn't catch the case where a lot of content is added
> by a commit hook (e.g. index updates) since commit hooks operate on the
> {{NodeBuilder}} level which is below {{Root}}.
> The aim of this issue is to pursue ways to push the purge logic further down
> below the {{NodeBuilder}} interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
