Hi Tomek, We are aiming at having a cluster of Oaks . I'll see if I can find the offending large string.
Thanks. -----Original Message----- From: Tomek Rekawek [mailto:reka...@adobe.com] Sent: 22 September 2016 15:29 To: oak-dev@jackrabbit.apache.org Subject: Re: oak-upgrade problems migrating from Jackrabbit 2 to Oak Hi Robert, I think the quoted exception may be caused by some long string stored in the Jackrabbit 2 repository. In MongoMK all the strings are inlined in the Mongo documents, while the binaries are extracted to the blob store. Therefore, string properties longer than ~15MB are not supported. It’s a hard limit of the Mongo implementation itself. Migrating this repository may require changing the repository structure - the large properties type should be changed from STRING to BINARY. As Torgeir noticed, SegmentMK doesn’t have such constraints. If you don’t need to create a cluster of Oaks, then SegmentMK is a better choice anyway. Regards, Tomek > On 22 Sep 2016, at 16:08, Robert Haycock > <robert.hayc...@artificial-solutions.com> wrote: > > Thanks Tomek, > > Getting closer! > > Looks like a setting somewhere needs increasing... > > Exception in thread "main" java.lang.RuntimeException: > javax.jcr.RepositoryException: Failed to copy content > at com.google.common.io.Closer.rethrow(Closer.java:149) > at > org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade.migrate(OakUpgrade.java:58) > at > org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade.main(OakUpgrade.java:42) > Caused by: javax.jcr.RepositoryException: Failed to copy content > at > org.apache.jackrabbit.oak.upgrade.RepositoryUpgrade.copy(RepositoryUpgrade.java:551) > at > org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade.upgrade(OakUpgrade.java:65) > at > org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade.migrate(OakUpgrade.java:53) > ... 1 more > Caused by: org.bson.BsonSerializationException: Size 24184261 is larger than > MaxDocumentSize 16793600. -- Tomek Rękawek | Adobe Research | www.adobe.com reka...@adobe.com
