Gerald, I think you missed Josh's reply here : https://lists.apache.org/thread.html/c5145461805429622a410c23c1199d578e146a5c94511b2d5833438b@%3Cdev.phoenix.apache.org%3E
Could you explain how using a subset of the pk columns to generate the salt byte helps with partitioning, aggregations etc? Thanks, Thomas On Thu, Sep 13, 2018 at 8:32 AM, Gerald Sangudi <gsang...@23andme.com> wrote: > Hi folks, > > Any thoughts or feedback on this? > > Thanks, > Gerald > > On Mon, Sep 10, 2018 at 1:56 PM, Gerald Sangudi <gsang...@23andme.com> > wrote: > >> Hello folks, >> >> We have a requirement for salting based on partial, rather than full, >> rowkeys. My colleague Mike Polcari has identified the requirement and >> proposed an approach. >> >> I found an already-open JIRA ticket for the same issue: >> https://issues.apache.org/jira/browse/PHOENIX-4757. I can provide more >> details from the proposal. >> >> The JIRA proposes a syntax of SALT_BUCKETS(col, ...) = N, whereas Mike >> proposes SALT_COLUMN=col or SALT_COLUMNS=col, ... . >> >> The benefit at issue is that users gain more control over partitioning, >> and this can be used to push some additional aggregations and hash joins >> down to region servers. >> >> I would appreciate any go-ahead / thoughts / guidance / objections / >> feedback. I'd like to be sure that the concept at least is not >> objectionable. We would like to work on this and submit a patch down the >> road. I'll also add a note to the JIRA ticket. >> >> Thanks, >> Gerald >> >> >
