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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/05/06 07:25:14 UTC

[jira] [Resolved] (OAK-1795) RepositoryUpgrade fails for very long path with DocumentNodeStore

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

Chetan Mehrotra resolved OAK-1795.
----------------------------------

    Resolution: Fixed

Applied the patch to trunk in [r1592658|http://svn.apache.org/r1592658] and merged to 1.0 in [r1592659|http://svn.apache.org/r1592659]

> RepositoryUpgrade fails for very long path with DocumentNodeStore
> -----------------------------------------------------------------
>
>                 Key: OAK-1795
>                 URL: https://issues.apache.org/jira/browse/OAK-1795
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.0, 1.1
>
>         Attachments: OAK-1795-marcel.patch
>
>
> While upgrading repository using DocumentNodeStore with Mongo if source repository contains nodes with very path containing name which are very long (greater than 150 bytes (OAK-333). This would trip the whole upgrade
> As such path cannot be supported for now it should be ensured that such cases should not trip whole upgrade. Instead upgrade process should skip such paths and log them as a warning



--
This message was sent by Atlassian JIRA
(v6.2#6252)