jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@adobe.com>
Subject Re: Conversion Mechanism for Non-Bundle PM Repositories?
Date Wed, 09 Jan 2013 09:37:31 GMT
the corresponding jira container issue is

feel free to append ideas, patch there or create subtasks


On 1/9/13 8:33 AM, Thomas Mueller wrote:
> Hi,
> For migration options see
> http://wiki.apache.org/jackrabbit/BackupAndMigration
> There is no migration tool specially for Oak yet. It would be great of
> course if you could write such a tool and contribute it!
> Regards,
> Thomas
> On 1/8/13 9:44 PM, "Melanie Drake"<melanie.drake@gmail.com>  wrote:
>> Since it seems that non-bundle persistence managers may become unsupported
>> in Jackrabbit 3.0, is there a plan to provide a data conversion mechanism
>> to convert 'simple schema' (e.g., Jackrabbit 1.6.1) repositories to the
>> new
>> schema?  I¹m not sure of the typical use of Jackrabbit, but I have many
>> customers who have amassed large amounts of data using Jackrabbit 1.6.1.
>> We
>> want to continue to use Jackrabbit, but we will be unable to upgrade if we
>> cannot retain this data.
>> (From what I understand, Oak may or may not be Jackrabbit 3.0.  I¹m just
>> wondering if a data conversion mechanism will be provided once the
>> non-bundle persistence managers are no longer supported.)
>> From the 2.2.0 release notes:
>> "Deprecation of old persistence managers.  All non-bundle persistence
>> managers and also non-pooled bundle database persistence managers have
>> been
>> deprecated in preparation for potential future changes of the persistence
>> layer.  All the deprecated persistence managers will remain functional and
>> supported in future 2.x releases, but will most likely be removed in
>> Jackrabbit 3.0"
>> Thanks!

View raw message