1) OK, i see we're getting to the point. The idea is then to try to
understand how OPP chooses Tokens and create vertices' keys as those.
This way i'd have my warranties. i could create an empty row with the
Token key and the following keys related to that vertex would have it as
a prefix. Does tha
1) Don't have anything to hand, other than to say the tokens for the OPP are the keys themselves. If your tokens are UUID are the sequential (version 1) UUIDs ? If so you can create a UUID for a known time, with the non type bytes all set high and use that as a token value. Otherwise you will need
@Adi:
Yes, that's exactly the reason for the OPP in the Subject :)
@Aaron:
Thanks for the complete answer.
1) In my case "vertexid_" is a uuid. Could you send me some reference on
how to achieve this partitioning based on this prefix and
orderpreservingpartitioning? I can't find docs about it.
>>1) "So if your node tokens are set as "vertexid_" all keys with the same
prefix will be in the same range."
Adding to Aaron's comment -
This will be the case if you use OrderPreservingPartitioner.
RandomPartitioner(the default) will distribute the tokens randomly across
nodes.
On Mon, Nov 15,
Rows are distributed around the cluster according to the ordering from the Partitioner used, and the Replication Strategy. All data for the same key will be stored together, and then replicated RF times. To answer your questions...1) Each node is responsible for the keys between the previous nodes
