As long as they are all of the person family (or some pre-existing columnfamily), that should be fine (and during updates you prefix Map keys with columnfamily name). You'll have person:name, person:address and person:email. If three months down the road you add nail color, and you do an update, the new 'nail color' attribute will be added as 'person:nail color'.
St.Ack On Wed, Nov 5, 2008 at 11:49 PM, Michael Dagaev <[EMAIL PROTECTED]>wrote: > Hi, Hui > > It is Ok if "Person" (in my example) is a class > with "name", "address", and "email" fields. > > However, what if this "Person" is just a map, > where "name", "address", and "email" are keys > I do not know in advance ? > > Thank you for your cooperation, > M. > > On Tue, Nov 4, 2008 at 8:51 PM, Ding, Hui <[EMAIL PROTECTED]> wrote: > > Why do you need to compare it? Just store a new version for every > > attribute/column that is not null. > > > > -----Original Message----- > > From: Michael Dagaev [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, November 04, 2008 10:32 AM > > To: [email protected] > > Subject: [LIKELY JUNK]Question on update > > > > Hi, all > > > > Let there is a row in People table. The column family Details > > consists of name, address, and email. > > Now I have a Person object which corresponds to this row. This object > > contains name and address > > but email is null. > > > > In order to update the row with the new data from the Person > > object. I have to read the row, compare it > > with my object and store only the difference. Is it correct? > > > > Thank you for your cooperation, > > M. > > >
