[
https://issues.apache.org/jira/browse/JCR-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788102#action_12788102
]
Thomas Mueller commented on JCR-1517:
-------------------------------------
I'm wondering if it still makes sense to solve this, or if it's better to use a
the repository migration as documented in
http://wiki.apache.org/jackrabbit/BackupAndMigration
> Global datastore and namespace index cause problems when migrating workspaces
> -----------------------------------------------------------------------------
>
> Key: JCR-1517
> URL: https://issues.apache.org/jira/browse/JCR-1517
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> 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.
