jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "matthew.l.donnelly" <mdonne...@proteuseng.com>
Subject Re: AW: NoSql Support
Date Wed, 17 Aug 2011 13:35:28 GMT

I was going to start looking into this project the next iteration. 

Getting this working is pretty much not an option for me :)  At that point,
my impl would probably be considered a rogue project.

The only other options I see are storing operations and serialized bundles
in memory for rollback(extremely dangerous).  Or writing the operations and
serialized bundles out to the file system(extremely ugly).

I'd be extremely nervous about storing the operations within hbase itself.

If you check out the BundleDbPersistenceManager and figure out a clean way
to do transaction management, please let me know!


>Thanks Jukka, 

>Depending on the data layout different solutions are possible. 

>If there's a finite depth of the tree than one or more final levels could 
>be encoded in a single row. There's virtually an infinite number of 
>columns you could have on a single row (by default limited to 250MB) 
>If more than one row needs update an optimistic locking mechanism could be 

>Again, it depends on the constraints (tree depth, nodes per level number, 


View this message in context: http://jackrabbit.510166.n4.nabble.com/NoSql-Support-tp3726565p3749984.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

View raw message