Sorry for the confusion created. I need to store emails registered
just for a single application. So although my data model would fit
into just a single row. But is storing a hundred million columns(col
name size= 8 byte; col value size=4 byte ) in a single row a good idea
? I am very much
What about if I spread these columns across 20 rows ? Then I have to
query each of these 20 rows for 500 columns. but still this seems a
better solution than one row for all cols or separate row for each
email id approaches !?
On Fri, Jul 27, 2012 at 11:36 AM, Aklin_81 asdk...@gmail.com wrote:
In general I believe wide rows (many cols ) are preferable to skinny rows
(many rows) so that you can get all the information in 1 go,
One can store 2 billion cols in a row.
However, on what basis would you store the 500 email ids in 1 row? What
can be the row key?
For e.g. If the query you want
