[
https://issues.apache.org/jira/browse/OAK-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-203:
--------------------------
Fix Version/s: (was: 1.1)
1.1.0
> Basic same name sibling support
> -------------------------------
>
> Key: OAK-203
> URL: https://issues.apache.org/jira/browse/OAK-203
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Jukka Zitting
> Assignee: Michael Dürig
> Priority: Minor
> Fix For: 1.1.0
>
> Attachments: OAK-203.patch
>
>
> There are some cases where clients or even the JCR spec expect same name
> siblings to be supported. We should have some mechanism to allow such cases
> to work with no or minimal required changes. Such a mechanism doesn't need be
> fully compliant with the SNS feature as specified by JCR, just good enough to
> to cover the most common use cases.
> My initial thinking on this is that, whichever way we end up implementing
> this, it would be nice if the underlying oak-core and microkernel -level SNS
> nodes simply used the "name[index]" naming pattern with no extra semantics
> associated with it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
