[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409573#comment-13409573
]
Jukka Zitting commented on OAK-169:
-----------------------------------
bq. At some point we will need to decide if we want efficient for support large
child node lists combined with orderable nodes.
That's what I was trying to say before we got sidetracked. I'd say we simply
decide not to support such cases until someone comes up with a compelling
enough use case (can't be backwards compatibility with Jackrabbit, since
Jackrabbit has never supported large child node lists). Carsten brought up a
few interesting cases, but since I know of no other database or file system
with inherent JCR-like ordering functionality for such cases, I don't think we
should go out of our way trying to directly support them with this feature.
> 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
