Hi
Assume I have a table with composite keys, say (x,y) salted into 3 buckets.
I understand that the salt is prepended to the actual rowkey. Now when I
try to lookup the table for x, will phoenix still do a range scan in 3
regions to fetch the result? How is the hash derived, using x or x,y?
Ideally I want to specify the hash component of the composite key,in this
case x thereby ensuring identical x's fall into the same region.Is it
possible in phoenix?

Regards,
Skanda

Reply via email to