Re: deduct token values for BOP

2011-07-07 Thread Richard Low
On Thu, Jul 7, 2011 at 3:39 PM, A J wrote: > Thanks. The above works. > But when I try to use the binary values rather than the hex values, it > does not work. i.e. instead of using 64ff, I use 01100100. Instead of > 6Dff, I use 01101101. > When using the binary values, everything (strings startin

Re: deduct token values for BOP

2011-07-07 Thread A J
Thanks. The above works. But when I try to use the binary values rather than the hex values, it does not work. i.e. instead of using 64ff, I use 01100100. Instead of 6Dff, I use 01101101. When using the binary values, everything (strings starting with a to z) seem to be going to n1 only. Any idea w

Re: deduct token values for BOP

2011-07-06 Thread Richard Low
On Wed, Jul 6, 2011 at 3:06 PM, A J wrote: > I wish to use the order preserving byte-ordered partitioner. How do I > figure the initial token values based on the text key value. > Say I wish to put all keys starting from a to d on N1. e to m on N2 > and n to z on N3. What would be the initial_toke

deduct token values for BOP

2011-07-06 Thread A J
I wish to use the order preserving byte-ordered partitioner. How do I figure the initial token values based on the text key value. Say I wish to put all keys starting from a to d on N1. e to m on N2 and n to z on N3. What would be the initial_token values on each of the 3 nodes to accomplish this ?