On Mon, Jun 27, 2011 at 12:02 PM, Philippe wrote:
> a quick followup on this : when using Byte ordered partitioner. how does a
> short key get mapped to the 128bit token ? what about keys longer than 128 ?
> does Cassandra just pad and truncate ?
Token are not limited to 128 bits. With the ordere
a quick followup on this : when using Byte ordered partitioner. how does a
short key get mapped to the 128bit token ? what about keys longer than 128 ?
does Cassandra just pad and truncate ?
thanks
Le 24 juin 2011 04:53, "Maki Watanabe" a écrit :
> A little addendum
>
> Key := Your data to identi
thanks guys. That clears things up.
On Jun 24, 2011, at 4:53 AM, Maki Watanabe wrote:
> A little addendum
>
> Key := Your data to identify a row
> Token := Index on the ring calculated from Key. The calculation is
> defined in replication strategy.
>
> You can lookup responsible nodes (endpoint
A little addendum
Key := Your data to identify a row
Token := Index on the ring calculated from Key. The calculation is
defined in replication strategy.
You can lookup responsible nodes (endpoints) for a specific key with
JMX getNaturalEndpoints interface.
maki
2011/6/24 aaron morton :
> Vario
Various places in the code call IPartitioner.decorateKey() which returns a
DecoratedKey which contains both the original key and the Token
The RandomPartitioner md5 to hash the key ByteBuffer and create a BigInteger.
OPP converts the key into utf8 encoded String.
Using the token to find which
Hi -
I'd like to understand more how the token is hashed with the key to determine
on which node the data is stored - called decorating in cassandra speak.
Can anyone share any documentation on this or describe this more in detail?
Yes, I could look at the code, but I was hoping to be able to
