jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1517) Global datastore and namespace index cause problems when migrating workspaces
Date Thu, 03 Apr 2008 00:16:32 GMT

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

Tobias Bocanegra updated JCR-1517:
----------------------------------

    Attachment: jcr-1517.r644105.patch

suggested patch uses nameIndex instead of nsIndex.

> Global datastore and namespace index cause problems when migrating workspaces
> -----------------------------------------------------------------------------
>
>                 Key: JCR-1517
>                 URL: https://issues.apache.org/jira/browse/JCR-1517
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.4
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>         Attachments: jcr-1517.r644105.patch
>
>
> Issue JCR-669 introduced a global namespace index. this is used by some persistence managers
in order to
> keep the serialization of names small (fewer bytes).
> unfortunately this forms a problem when a workspace needs to be migrated to another repository
with other namespace indexes. so an easy migration is not possible unless you export/import
the entire workspace using system view (which is almost impossible for huge workspaces).
> another potential problem is cause by the global data store, since all workspaces share
the same.
> so when migrating a workspace, you would need to transfer all respective records in the
datastore to the target repository.
> where the datastore problem can be solved by copying the respective items, the namespace
indexes are a bigger problem, since the serialized items need to be adjusted.
> suggest to alter the bundle pm to use the 'name index' for the namespaces as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message