Re: Migration without an embedded Jackrabbit

Hi, On Fri, Oct 11, 2013 at 4:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: ...I've been thinking about the upgrade/migration code (oak-upgrade, OAK-458) over the past few days, and trying to figure out how we could achieve that without having to keep the full Jackrabbit 2.x codebase as

Re: Migration without an embedded Jackrabbit

Hi I see the problem and I agree that this in fact *is* a problem. But I still don't agree with an integrated, transparent solution to this upgrade problem. And I never will -- such application bloat and even code duplication along with testing and maintenance etc. requirements just sound

Re: Migration without an embedded Jackrabbit

Hi, On Mon, Oct 14, 2013 at 4:38 AM, Felix Meschberger fmesc...@adobe.com wrote: IMNSHO migration of Jackrabbit 2 based repositories to Oak is a one-shot problem: you apply this once to a repository and be done. So why load the application with a host of unneeded pieces ? I'd like to make

Re: Migration without an embedded Jackrabbit

Hi Thanks for the clarifications. Yet, they more confirm my first impression than they resolve the concerns. Particularly your timing and smoothness assumptions. Migrating JR2 to Oak is much more complex than migrating from one version of JR2 to the next. I would even assume it is way more

jackrabbit-oak build #2356: Broken

Build Update for apache/jackrabbit-oak - Build: #2356 Status: Broken Duration: 697 seconds Commit: d7f0f180356798d32e8d08d276f256b75fb060b9 (trunk) Author: Alexandru Parvulescu Message: OAK-1093 IllegalArgumentException on Row.getValues() git-svn-id:

Re: Migration without an embedded Jackrabbit

Hi, On Mon, Oct 14, 2013 at 4:27 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Would this be a problem is there was a way for this additional dependency to go away after startup, once the migration is done? Yes, all the required code would go the oak-upgrade bundle that can be dropped

buildbot failure in ASF Buildbot on oak-trunk

The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/3424 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp:

Re: jackrabbit-oak build #2356: Broken

oups, sorry about that. I'm on it On Mon, Oct 14, 2013 at 3:15 PM, Travis CI ju...@apache.org wrote: Build Update for apache/jackrabbit-oak - Build: #2356 Status: Broken Duration: 697 seconds Commit: d7f0f180356798d32e8d08d276f256b75fb060b9 (trunk)

buildbot success in ASF Buildbot on oak-trunk

The Buildbot has detected a restored build on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/3426 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

Re: Migration without an embedded Jackrabbit

Hi, On Mon, Oct 14, 2013 at 9:09 AM, Felix Meschberger fmesc...@adobe.com wrote: Thanks for the clarifications. Yet, they more confirm my first impression than they resolve the concerns. Particularly your timing and smoothness assumptions. Migrating JR2 to Oak is much more complex than

jackrabbit-oak build #2357: Still Failing

Build Update for apache/jackrabbit-oak - Build: #2357 Status: Still Failing Duration: 912 seconds Commit: 904d8f44b53e8059737c5b74efda7e69c1892dbb (trunk) Author: Thomas Mueller Message: OAK-641: Improved benchmark tooling - use a different node name each

jackrabbit-oak build #2360: Still Failing

Build Update for apache/jackrabbit-oak - Build: #2360 Status: Still Failing Duration: 785 seconds Commit: 0487a5b0c7375639b0071be0e65347357ffd2b1b (trunk) Author: Thomas Mueller Message: OAK-123 Data store: improved error message git-svn-id:

Re: jackrabbit-oak build #2360: Still Failing

observationDisposeFromListener[2](org.apache.jackrabbit.oak.jcr.observation.ObservationTest): Timeout waiting for task. On Mon, Oct 14, 2013 at 4:00 PM, Travis CI ju...@apache.org wrote: Build Update for apache/jackrabbit-oak - Build: #2360 Status: Still

jackrabbit-oak build #2358: Fixed

Build Update for apache/jackrabbit-oak - Build: #2358 Status: Fixed Duration: 1697 seconds Commit: 531aca786416e57fa1951e486bf569e0146b0102 (trunk) Author: Alexandru Parvulescu Message: OAK-1093 IllegalArgumentException on Row.getValues() - null guard

jackrabbit-oak build #2359: Fixed

Build Update for apache/jackrabbit-oak - Build: #2359 Status: Fixed Duration: 1836 seconds Commit: 667291aa5c4d9ce9e2d438a0612d1ca17e5e5f12 (trunk) Author: Thomas Mueller Message: OAK-762 MongoMK: automatic unique cluster id / revision order depends on the

jackrabbit-oak build #2361: Fixed

Build Update for apache/jackrabbit-oak - Build: #2361 Status: Fixed Duration: 1674 seconds Commit: e2d3ebc211133c41ea268f2b3c889d2c907755b2 (trunk) Author: Angela Schreiber Message: OAK-1095 : versionable path property has wrong type git-svn-id:

Re: Migration without an embedded Jackrabbit

Hi, I second Felix' comments and prefer a standalone upgrade tool. this does not mean that an upgrade is always a manual step. the embedding application (e.g. Sling) can still contain the tool and auto-upgrade if desired. I even think that a migration could be done purely on the JCR level, for

Re: content hash of a tree

On Mon, Oct 14, 2013 at 7:08 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Mon, Oct 14, 2013 at 8:39 PM, Tobias Bocanegra tri...@apache.org wrote: just wondering, how can I retrieve the content-hash of a subtree? You can't. The underlying MicroKernel/NodeStore does not