On Tue, Mar 1, 2011 at 10:36 PM, Shaun Cutts wrote:
> This isn't quite true, I think. RandomPartitioner uses MD5. So if you had
> 10^16 rows, you would have a 10^-6 chance of a collision, according to
> http://en.wikipedia.org/wiki/Birthday_attack ... and apparently MD5 isn't
> quite balanced, so
This isn't quite true, I think. RandomPartitioner uses MD5. So if you had 10^16
rows, you would have a 10^-6 chance of a collision, according to
http://en.wikipedia.org/wiki/Birthday_attack ... and apparently MD5 isn't quite
balanced, so your actual odds of a collision are worse (though I'm not
Thanks Sylvain
On Wed, Feb 16, 2011 at 10:05 AM, Sylvain Lebresne wrote:
> Sky is the limit.
>
> Columns in a row are limited to 2 billion because the size of a row is
> recorded in a java int. A row must also fit on one node, so this also limit
> in a way the size of a row (if you have large val
Sky is the limit.
Columns in a row are limited to 2 billion because the size of a row is
recorded in a java int. A row must also fit on one node, so this also limit
in a way the size of a row (if you have large values, you could be limited
by this factor much before reaching 2 billions columns).
is there a limit or a factor to take into account when the number of rows in
a CF exceeds a certain number? i see the columns for a row can get upwards
of 2 billion ... can i have 2 billion rows without much issue?
--
Sasha Dolgy
sasha.do...@gmail.com
