[
https://issues.apache.org/jira/browse/TRAFODION-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652485#comment-14652485
]
Hans Zeller commented on TRAFODION-781:
---------------------------------------
The syntax I would like to propose is a new, optional "IN <r> REGIONS" clause:
SALT USING <p> PARTITIONS {color:red}[ IN <r> REGIONS ]{color} [ ON
(<column(s)>) ]
If the clause is not specified, the behavior will be as today, the table is
pre-split into p regions. If specified, _r_ must be greater than or equal to 1
and less than or equal to _p_.
For those of us who want to make it grammatically correct, "REGION" instead of
"REGIONS" is also accepted, for the case of 1 initial region.
If _r_ = 1, we should not apply the
org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy split
policy, like we do for other salted tables.
> LP Bug: 1394783 - To allow for future growth, we should allow multiple salt
> values per region during the initial create table
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TRAFODION-781
> URL: https://issues.apache.org/jira/browse/TRAFODION-781
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp
> Reporter: Hans Zeller
> Assignee: Hans Zeller
> Fix For: 2.0-incubating
>
>
> This is something Rohit pointed out:
> To allow for future growth, we should have a larger number of salt values for
> salted tables. Initially, there may not be a need to create a separate HBase
> region for each one of these. We could allow the user to specify two numbers
> at table creation time a) the number of salt values and b) the number of
> HBase regions to create.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
