incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Strauss <da...@fourkitchens.com>
Subject Re: ColumnFamilies vs composite rows in one table.
Date Fri, 05 Mar 2010 18:33:33 GMT
On 2010-03-05 18:30, David Strauss wrote:
> On 2010-03-05 18:04, Erik Holstad wrote:
>> So you can either have
>> ColumnFamilyFrom:userTo:{userFrom->messageid}
>> ColumnFamilyTo:userFrom:{userTo->messageid}
>>
>> or something like
>> ColumnFamily:user_to:{user1_messageId, user2_messageId}
>> ColumnFamily:user_from:{user1_messageId, user2_messageId}
> 
> You've changed two different things between the examples:
> 
> (1) Whether direction is distinguished by the key or by the CF.
> (2) Something about the columns, but this isn't clear or necessary to
> support the change in CF/key structure.

Upon further inspection, the first example appears to use the other
party to a message as the column name. That will only allow one
messageid for any unique <direction, userA, userB>. That seems broken to me.

-- 
David Strauss
   | david@fourkitchens.com
Four Kitchens
   | http://fourkitchens.com
   | +1 512 454 6659 [office]
   | +1 512 870 8453 [direct]


Mime
View raw message