phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1135) Add custom split policy to salted tables to ensure a salt bucket cannot span a region
Date Thu, 28 Aug 2014 01:11:57 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113155#comment-14113155
] 

James Taylor commented on PHOENIX-1135:
---------------------------------------

When this gets done, we should also remove the following check in SchemaUtil.processSplit(),
as it will no longer be necessary:
{code}
        if (splits.length > 0 && saltBucketNum != null && defaultRowKeyOrder)
{
            throw new SQLExceptionInfo.Builder(SQLExceptionCode.NO_SPLITS_ON_SALTED_TABLE).build().buildException();
        }
{code}

> Add custom split policy to salted tables to ensure a salt bucket cannot span a region
> -------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1135
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1135
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> Our salting logic relies on the salt bucket (i.e. the first byte of the row key) to be
the same within a region. We should add a custom split policy automatically when the table
is created to guarantee this.



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

Mime
View raw message