Your requirement is still not quite clear - are you counting users or
reports, or reports of a type for each user, or...?
You can have a separate table, with the partition key being the user type,
and using the user id as a clustering column - provided that the number of
users is only thousands or
,
Matthew
*From:* Shahab Yunus [mailto:shahab.yu...@gmail.com]
*Sent:* 03 June 2015 15:55
*To:* user@cassandra.apache.org
*Subject:* Re: How to store denormalized data
Suggestion or rather food for thought
Do you expect to read/analyze the written data right away? Or will it be a
batch
Suggestion or rather food for thought
Do you expect to read/analyze the written data right away? Or will it be a
batch process, kicked off later in time? What I am trying to say is that if
the 'read/analysis' part is a) batch process and b) kicked off later in
time, then #3 is a fine solution?
