You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Daniel Sbityakov <Da...@kyndryl.com.INVALID> on 2023/02/07 18:33:03 UTC

Upgrading jackrabbit repo to oak

Hi all,

I have been trying to run the oak-upgrade tool (ver. 1.46.0) to see what it would take to upgrade our existing jackrabbit repository (ver. 2.21.8).  Both source and target repositories will be using an Oracle store.

I am using this guide https://jackrabbit.apache.org/oak/docs/migration.html, but it does not look like this migration using two jdbc urls is supported since the only StoreType value that constructs an instance of Jackrabbit2Factory is StoreType#JCR2_DIR_XML, but which also returns false from its #matches() method.

Can someone please confirm what is the preferred way to upgrade from Jackrabbit jdbc-based repository to a new Oak target?
Let me know also if I should create a git issue and document this there.

Thanks very much!

Daniel Sbityakov
Technical Architect
Services for Managed Applications
1 919 698 2054 Mobile
Daniel.Sbityakov@kyndryl.com
[signature_1963250538]

Re: Upgrading jackrabbit repo to oak

Posted by Julian Reschke <ju...@gmx.de>.
On 07.02.2023 19:33, Daniel Sbityakov wrote:
> Hi all,
>
> I have been trying to run the oak-upgrade tool (ver. 1.46.0) to see what
> it would take to upgrade our existing jackrabbit repository (ver.
> 2.21.8).  Both source and target repositories will be using an Oracle store.
>
> I am using this guide
> https://jackrabbit.apache.org/oak/docs/migration.html
> <https://jackrabbit.apache.org/oak/docs/migration.html>, but it does not
> look like this migration using two jdbc urls is supported since the only
> StoreType value that constructs an instance of Jackrabbit2Factory is
> StoreType#JCR2_DIR_XML, but which also returns false from its #matches()
> method.
>
> Can someone please confirm what is the preferred way to upgrade from
> Jackrabbit jdbc-based repository to a new Oak target?
>
> Let me know also if I should create a git issue and document this there.
>
> Thanks very much!
>
> *Daniel Sbityakov*
>
> Technical Architect

Hi Daniel,

I have zero experience with migration.

That said: the work on the OAK RDB persistence essentially is frozen; I
would be very reluctant to migrate a production system onto it. If you
need clustering, the choice should be the MongoDB persistence.

Best regards, Julian