[
https://issues.apache.org/jira/browse/OAK-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253703#comment-15253703
]
Tomek Rękawek commented on OAK-4260:
------------------------------------
Commited [the
change|https://github.com/trekawek/jackrabbit-oak/commit/ff4b7fc1d367ac87a12fe2c37cdcde73d665916a]
to my private github branch. There's a functional test migrating segment to
segment-next and it works.
It registers a new schema for the oak-upgrade, {{segment-next:}}. A migration
may look like this:
{noformat}
java -jar oak-upgrade.jar --mmap crx-quickstart/repository
segment-next:crx-quickstart/new-repository
{noformat}
The {{segmentstore}} directory inside the passed arguments will be accessed and
created.
> Define and implement migration from oak-segment to oak-segment-next
> -------------------------------------------------------------------
>
> Key: OAK-4260
> URL: https://issues.apache.org/jira/browse/OAK-4260
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-next, segmentmk
> Reporter: Michael Dürig
> Assignee: Tomek Rękawek
> Labels: migration
> Fix For: 1.6
>
>
> We need to come up with a plan, implementation and documentation for how we
> deal with migrating from {{oak-segment}} to {{oak-segment-next}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
