I don't say you shouldn't. In case you feel like there is a problem, you may think of splitting column families into N. But I think you won't get that problem. You can read about RowCacheSize and KeyCache support on 0.7.X of Cassandra, if you rows are small, you may cache a lot of them and avoid a lot of latency issues when reading writing.
On Thu, Feb 24, 2011 at 4:18 PM, mcasandra <mohitanch...@gmail.com> wrote: > > Thanks! I am thinking more in terms where you have millions of keys (rows). > For eg: UUID as a row key. or there could millions of users. > > So are we saying that we should NOT create column families with these many > keys? What are the other options in such cases? > > UserProfile = { // this is a ColumnFamily > > 1 { // this is the key to this Row inside the CF > > // now we have an infinite # of columns in this row > > username: "phatduckk", > > email: "[hidden email]", > > phone: "(900) 976-6666" > > }, // end row > > 2 { // this is the key to another row in the CF > > // now we have another infinite # of columns in this row > > username: "ieure", > > email: "[hidden email]", > > phone: "(888) 555-1212" > > age: "66", > > gender: "undecided" > > }, > > } > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understanding-Indexes-tp6058238p6061574.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >