On Wed, 2012-09-05 at 13:23 +1200, aaron morton wrote:
I believe the question is why is the maximum 2**127 and not
0x
oops - I got the wrong number of digits there.
The maximum is the size of the digest created by MD5.
(I may be mistaken) - isn't the range of MD5 values
0
I meant that what the OP spotted was it's an inclusive maximum =
That's it Tim, you understood what I meant. Thank you for taking the time
to consider my question.
0 = hash (2**127) corresponds to the cyclic group Z/(2**127) so the
maximum is (2**127)-1
So there is indeed a mix up in sources
A little clarification. When I talk about exclusive bounds, I mean:
compareTo(ZERO) = 0 or compareTo(MAXIMUM) = 0
I believe the question is why is the maximum 2**127 and not
0x
The maximum is the size of the digest created by MD5.
Does that answer the question?
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/09/2012, at 8:20 PM, Tim
On Tue, 2012-08-28 at 16:57 +1200, aaron morton wrote:
Sorry I don't understand your question.
Can you explain it a bit more or maybe someone else knows.
I believe the question is why is the maximum 2**127 and not
0x
Tim
Cheers
-
Aaron Morton
Sorry I don't understand your question.
Can you explain it a bit more or maybe someone else knows.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 27/08/2012, at 7:16 PM, Romain HARDOUIN romain.hardo...@urssaf.fr wrote:
Thank you
AbstractHashedPartitioner
does not exist in the trunk.
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commitdiff;h=a89ef1ffd4cd2ee39a2751f37044dba3015d72f1
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 24/08/2012, at 10:51
Hi,
AbstractHashedPartitioner defines a maximum of 2**127 hence an order of
(2**127)+1.
I'd say that tokens of such partitioners are intented to be distributed in
Z/(127), hence a maximum of (2**127)-1.
Could there be a mix up between maximum and order?
This is a detail but could someone
