Hi Sasha,
There's been a lot of fud in regards to SuperColumns. But actually in
our case we found them quite useful.
The main argument for using SC in that case is that message metadata is
immutable and in most of the cases read and written alltogether (i.e.
you fetch all message headers together). There are few exceptions when
we need to update only one column, e.g. when updating labels/markers.
But the number of such requests shouldn't affect performance
dramatically.
Currently we have this model running in prod with 150K subs and 20M
messages and quite happy with the performance.
Would be interesting to see other alternatives though.
Regards,
Rustam.
On Fri Dec 16 11:51:24 2011, Sasha Dolgy wrote:
Hi Rustam,
Thanks for posting that.
Interesting to see that you opted to use Super Column's:
https://github.com/elasticinbox/elasticinbox/wiki/Data-Model ..
wondering, for the sake of argument/discussion .. if anyone can come
up with an alternative data model that doesn't use SC's.
-sd
On Fri, Dec 16, 2011 at 11:10 AM, Rustam Aliyev<rus...@code.az> wrote:
Hi Sasha,
Replying to the old thread just for reference. We've released a code which
we use to store emails in Cassandra as an open source project:
http://elasticinbox.com/
Hope you find it helpful.
Regards,
Rustam.
On Fri Apr 29 15:20:07 2011, Sasha Dolgy wrote:
Great read. thanks.
On Apr 29, 2011 4:07 PM, "sridhar basam"<s...@basam.org
<mailto:s...@basam.org>> wrote:
Have you already looked at some research out of IBM about this usecase?
Paper is at
http://ewh.ieee.org/r6/scv/computer/nfic/2009/IBM-Jun-Rao.pdf
Sridhar
