You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:17:46 UTC

[jira] [Resolved] (PHOENIX-353) question about salt buckets

     [ https://issues.apache.org/jira/browse/PHOENIX-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid resolved PHOENIX-353.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> question about salt buckets
> ---------------------------
>
>                 Key: PHOENIX-353
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-353
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Raymond Liu
>
> I can see that the doc mentioned that one extra bytes is added for row key, and this is calcuated by hash and mode to SALT_BUCKETS.  And then the table will be pre-split according to the SALT_BUCKETS
> While my question is:
> 1 why need to extend the length of the presplit key? just leave it with one byte, the extended length seems to me useless, if the region got split further by hbase, hbase will take care of it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)