[
https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729069#action_12729069
]
Paco Avila commented on JCR-1972:
---------------------------------
As I wrote some time ago, these modifications make two enhacements in the
jackrabbit-core functionality:
- Enable UUID parameter in addNode: this allow to preserve the unique node
identifier across a repository migration. If you use references this change is
fundamental.
- Enable Calendar parameter in checkin: this change can be used to preserve
checking date in document version history in a possible migration.
This migration can be of two types:
- Change the repository backend: you use the default Derby database, but you
want to swith to MySQL, for example. Actually this is not possible in a easy
way.
- Change the repository node definitions: jackrabbit actually can't deal with
these changes depending on their complexity. You have to write a program to
make this migration.
>From my point of view, this patch introduces very neccessary funtionality into
>Jackrabbit. If you want to include these modifications in a near release, I
>can try to send a new patch that works with an specific jackrabbit-core
>version.
> Preserving UUID and document version history on repository migration
> --------------------------------------------------------------------
>
> Key: JCR-1972
> URL: https://issues.apache.org/jira/browse/JCR-1972
> Project: Jackrabbit Content Repository
> Issue Type: Wish
> Components: jackrabbit-core
> Affects Versions: core 1.4.8
> Reporter: Paco Avila
> Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch
>
>
> I have been working I an migration utility for OpenKM and I performed some
> changes in jackrabit-core to enable version import, preserving
> the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to
> preserve UUID in the migration process.
> This migration process is needed because there are changes in repository node
> definition, and Jackrabbit can't deal with this actually.
> I've attache a PDF with the changes needed in Jackrabbit-core. It works and
> there was no problems with the migrated repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
