[
https://issues.apache.org/jira/browse/OAK-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816592#comment-17816592
]
Julian Reschke commented on OAK-10642:
--------------------------------------
Do you see the branch commits happening?
> Add tests for operations on very large ordered collections
> ----------------------------------------------------------
>
> Key: OAK-10642
> URL: https://issues.apache.org/jira/browse/OAK-10642
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: core, jcr
> Reporter: Manfred Baedke
> Assignee: Manfred Baedke
> Priority: Major
>
> The ordering is persisted in a single multi-valued string property containing
> the names of the children in the correct order, which is prone to run into
> property size limits or even document size limits and also may perform poorly.
> One concern in particular is the possibility to run into Mongo's document
> size limit of 16M with long transactions containing many operations that
> change the ordering (or insert/remove), eventually triggering branch commits
> that will be stored in a single Mongo document quickly growing in size
> because of the weird data model used to persist the ordering.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
