Re: MongoMK^2 design proposal

Hi, I'm a bit skeptical if the added complexity is worth the disk space saving. As for disk space: when storing data as JSON (as I guess 99% of all users of MongoDB do), MongoDB compresses the data as well. Currently the format seems to be BSON, and there are plans to Snappy / LZO / LZ4. See

Re: MongoMK^2 design proposal

Hi, On Thu, Feb 14, 2013 at 10:52 AM, Thomas Mueller muel...@adobe.com wrote: So I guess disk space and memory usage is just different, but it's not so easy to say whether it's better or worse. Indeed. Ultimately we'll need higher-level performance benchmarks to properly evaluate these things.

Add the #setHook method to the NodeStore?

hi guys, I'm wondering if we could promote the #setHook method to the NodeStore api? CommitHooks are an important part of Oak and all the existing implementations have one anyway. thanks, alex

Re: Add the #setHook method to the NodeStore?

Hi, On Thu, Feb 14, 2013 at 1:13 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: I'm wondering if we could promote the #setHook method to the NodeStore api? The intention so far has been to keep NodeStore functionally equivalent to the MicroKernel, i.e. just a higher-level wrapper that

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/1573 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp:

Re: Add the #setHook method to the NodeStore?

hi I'm wondering if we could promote the #setHook method to the NodeStore api? The intention so far has been to keep NodeStore functionally equivalent to the MicroKernel, i.e. just a higher-level wrapper that hides details like caching, JSOP processing and revision/path tracking. Adding

Re: Add the #setHook method to the NodeStore?

see https://issues.apache.org/jira/browse/OAK-627 On 2/14/13 6:38 PM, Angela Schreiber wrote: hi I'm wondering if we could promote the #setHook method to the NodeStore api? The intention so far has been to keep NodeStore functionally equivalent to the MicroKernel, i.e. just a higher-level

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/1578 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

Re: svn commit: r1446225 - in /jackrabbit/oak/trunk/oak-mongomk/src: main/java/org/apache/jackrabbit/mongomk/prototype/ test/java/org/apache/jackrabbit/mongomk/prototype/

On 14.2.13 16:06, thom...@apache.org wrote: -@Ignore public void batchInsert() throws Exception { I reverted this part since it broke the build. Michael

commit hooks and indexing

Hi, AFAIK indexing currently uses commit hooks for keeping the index up to date when content changes. As Jukka mentioned this might not be the right thing to do since when a commit fails, we end up with invalid index entries. The conclusion was, that indexing should use the Observer, which

Re: Novel workspace idea

On Feb 14, 2013, at 8:27 , Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, When discussing workspaces and our options for implementing them, our main options so far have been: 1) No workspace support (with jcr:system just a normal subtree) 2) Workspaces as fully independent trees (each