Saw responses over on the Cassandra to a similar question and I think I've answered my own question...
the Timestamp you refer to could be the date, and the columns would be the milliseconds within that particular date? --Andrew On Apr 23, 2010, at 6:17 PM, Andrew Nguyen wrote: > When you say Bob-ABP-Timestamp, I assume you're still referring to the > row-key? If so, I'm confused as to what the column name would be. > > Or, are you saying that each row should be a combination of the patient name > and timestamp, with the physiologic parameter name as the column name? Would > that still provide better query times when only looking for a particular > patient's data? > > Thanks, > Andrew > > On Apr 23, 2010, at 6:06 PM, Erik Holstad wrote: > >> Hey Andrew! >> >> The storage structure of your data could be pretty much the same choosing >> HBase or Cassandra. >> You can either do it your way or >> Bob-ABP-Timestamp which will give you the advantage of scaling better, since >> both HBase and >> Cassandra are splitting by rows. >> >> HBase has the advantage of scanning much better than Cassandra and is >> therefore more suitable >> for the row oriented approach. >> >> Erik >
