To me, the culprit seems like first line of
`org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent.initialize`:
   builder.setProperty(JCR_PRIMARYTYPE, NT_REP_ROOT, Type.NAME);

which would the force
>    org.apache.jackrabbit.oak.plugins.memory.ModifiedNodeState.squeeze line: 
> 125
to read all children of root node.

While this could probably be done as an improvement in oak to
check-then-set behavior. But, as others noted, may be creating a very
flat hierarchy might lead to more troubles down the line.

Thanks,
Vikas

Reply via email to