Hi James, Does the fix work for a composite key? The reason I'm asking this question is that the salt is generated using composite key (x,y) but when I just look up on x, is it possible to identify the bucket? Please correct me if I'm wrong..
Thanks, Skanda -----Original Message----- From: "James Taylor" <[email protected]> Sent: 13-02-2014 00:42 To: "[email protected]" <[email protected]> Subject: Re: Composite rowkey and salting Hi Skanda, Yes, there was actually a bug here that was preventing a point lookup for salted tables: https://issues.apache.org/jira/browse/PHOENIX-20 It's been fixed and is in our release candidate build for 2.2.3. Would be great if you could verify that this solves your issue. Thanks, James On Wed, Feb 12, 2014 at 10:46 AM, Skanda <[email protected]> wrote: 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
