You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alex Deparvu (JIRA)" <ji...@apache.org> on 2018/09/28 09:49:00 UTC

[jira] [Updated] (OAK-7786) Make the NamespaceEditor less strict when enforcing changes to rep:nsdata node

     [ https://issues.apache.org/jira/browse/OAK-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Deparvu updated OAK-7786:
------------------------------
    Fix Version/s: 1.9.9
                   1.10

> Make the NamespaceEditor less strict when enforcing changes to rep:nsdata node
> ------------------------------------------------------------------------------
>
>                 Key: OAK-7786
>                 URL: https://issues.apache.org/jira/browse/OAK-7786
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>            Priority: Major
>             Fix For: 1.10, 1.9.9
>
>
> Following OAK-7510 changes there seem to be some scenarios where changes to {{rep:nsdata}} node trigger repository initialization issues.
> So far I had issues reproducing but they seem to be in the area of upgrade and store composite.
> I would like to reduce the strictness of the NamespaceEditor and instead of throwing an error it would rebuild its internal index node. The impact on performance would be tiny and becuase the node is rebuilt on each change there is no loss of integrity.
> Will be hiding this behind a flag so various scenarios can be tested, until this issue is clarified.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)