[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407998#comment-13407998
]
Michael Dürig commented on OAK-169:
-----------------------------------
There are two things being mixed up here:
# the guarantee of the repository to return the child nodes in some stable
order
# the ability to re-order child nodes
I think we should and can support 1. for any number of child nodes.
We can also support 2. through the {{oak:childOrder}} property approach for any
number of child nodes but with a linear performance degradation in the _number
of reorder operations_. To do this we just record the differences to the
natural order in the {{oak:childOrder}} property. It's a bit like remembering
each reorder operation and playing it back on access.
> Support orderable nodes
> -----------------------
>
> Key: OAK-169
> URL: https://issues.apache.org/jira/browse/OAK-169
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Reporter: Jukka Zitting
>
> There are JCR clients that depend on the ability to explicitly specify the
> order of child nodes. That functionality is not included in the MicroKernel
> tree model, so we need to implement it either in oak-core or oak-jcr using
> something like an extra (hidden) {{oak:childOrder}} property that records the
> specified ordering of child nodes. A multi-valued string property is probably
> good enough for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
