ionproto' that I receive has a field that is
recursive. How do I define a data model in Cassandra to store this
data. itemrelationproto
references itemgroupproto and itemgroupproto references itemrelationproto .
Thanks.
message itemrelationproto {
optional string i
Hi All,
The protobuf message 'sessionproto' that I receive has a field that is
recursive. How do I define a data model in Cassandra to store this
data. itemrelationproto
references itemgroupproto and itemgroupproto references itemrelationproto .
Thanks.
message itemrelationproto {
question that i'll be glad if you can help me or give me a
> > direction.
> >
> > I have an activity feed like the activity feed on Instagram. When user
> > (lets say UserA) enters his page he can see all the activities that are
> > related to him,
> &
user
> (lets say UserA) enters his page he can see all the activities that are
> related to him,
> for example, user B liked your post.user C commented on your post etc...
>
> the cassandra data model that i thought about is:
>
> userID UDID (partition key)
> d
liked your post.user C commented on your post etc...
>
> the cassandra data model that i thought about is:
>
> userID UDID (partition key)
> datetimeadded timestamp (clustering column DESC)
> userID_Name text
> userID_Picture_URL text
> userID_From UDID (this is userB from t
age he can see all the activities that are
related to him,
for example, user B liked your post.user C commented on your post etc...
the cassandra data model that i thought about is:
userID UDID (partition key)
datetimeadded timestamp (clustering column DESC)
userID_Name text
userID_Picture_URL text
u
Will answer on the user list.
Aaron
On 8/03/2011, at 1:11 AM, Baskar wrote:
> Does Cassandra allow nesting of column families?
>
> Here is the use case
> - we need to store calls made by employees
> - employees are associated with an account
> - accounts have phone numbers
> - many calls are m
Does Cassandra allow nesting of column families?
Here is the use case
- we need to store calls made by employees
- employees are associated with an account
- accounts have phone numbers
- many calls are made by employees for a given account and phone
If possible, would like to store call related
