Hi Oak-Devs

I wonder about the documentation at
http://jackrabbit.apache.org/oak/docs/nodestore/segmentmk.html

In the section "Node records" it's stated:

"A node that contains more than N properties or M child nodes (exact size
TBD, M ~ 1k) is stored differently, using map records for the properties
and child nodes. This way a node can become arbitrarily large and still
remain reasonably efficient to access and modify. The main downside of this
alternative storage layout is that the ordering of child nodes is lost."


Is this a valid statement for Oak 1.x? I would be really surprised, that
starting at an arbitrary number of childness the ordering of childnode gets
lost (for performance reasons). Can someone confirm?

Thanks!

-- 
Cheers,
Jörg Hoh,

http://cqdump.wordpress.com
Twitter: @joerghoh

Reply via email to