jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1126) Same node and property name support
Date Mon, 04 Nov 2013 15:53:18 GMT

    [ https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812930#comment-13812930
] 

Stefan Guggisberg commented on OAK-1126:
----------------------------------------

bq. If we do apply the patch, we should also update relevant parts of the MicroKernel API
and adjust the NodeStore documentation accordingly.

-1 for changing the MicroKernel API until we have a clear picture of the full impact of such
API changes.
the change would e.g. also affect the commit method and the json_diff format.  those changes,
if we agree on them, need to be carefully documented.

> Same node and property name support
> -----------------------------------
>
>                 Key: OAK-1126
>                 URL: https://issues.apache.org/jira/browse/OAK-1126
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core, doc, jcr
>            Reporter: Tobias Bocanegra
>         Attachments: OAK-1126.patch
>
>
> The initial MK abstraction mandated that the nodes and properties share the same namespace
(http://wiki.apache.org/jackrabbit/RepositoryMicroKernel#Data%20Model). This is a regression
from Jackrabbit 2.x, which supports same name nodes and properties (SNNP).
> OTOH, the NodeStores can easily support SNNP and with proper escaping, the MKs can also
support it.
> We should try to keep the support for SNNP in order to keep backward compatibility for
existing content, and also keep the support for importing XML documents with same attribute
and element names.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message