I had a quick look at DAO and my common uses case is, row names
appearing as column ID's elsewhere (indexes etc). I also wanted to track
deltas at a column level and have a reasonable sized client side cache.
I ended up with two abastract DAO's, one for Column Family, one for
Super column factory,
Thanks Anthony. Following your comments, I searched for a similar
approach using command pattern. http://code.google.com/p/casemate
seems a way of doing that.
On 27 July 2011 18:23, Ikeda Anthony wrote:
> Speaking from personal experience (and believe me it all comes down to this)
> we attempted
Speaking from personal experience (and believe me it all comes down to this) we
attempted a DAO approach as well. However, we found that based upon all the
mutator.addInsertion()s we were creating across column families everything
ended up in the same DAO - we only have 3 main Column Families th
Hi,
The question I am asking is a bit about the design of a data access
objects layer on top of a cassandra datastore.
I had a look at project Kundera which basically implies JPA approach
by creating POJOs and mapping them through annotations. Looks
promising but what if I would like to have new
