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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/06/03 11:08:59 UTC

[jira] [Updated] (OAK-4426) RepositorySidegrade: oak-segment to oak-segment-tar should drop the name length check

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

Tomek Rękawek updated OAK-4426:
-------------------------------
    Fix Version/s: 1.5.4
                   1.6

> RepositorySidegrade: oak-segment to oak-segment-tar should drop the name length check
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-4426
>                 URL: https://issues.apache.org/jira/browse/OAK-4426
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar, upgrade
>            Reporter: Alex Parvulescu
>            Assignee: Tomek Rękawek
>             Fix For: 1.6, 1.5.4
>
>
> As mentioned on OAK-4260, this name length verification is causing some data to be dropped from the upgrade. This limitation only affects mongomk deployments, so it should not apply here.
> {code}
> *WARN*  org.apache.jackrabbit.oak.upgrade.nodestate.NameFilteringNodeState - Node name 'node-name' too long.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)