[
https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103397#comment-13103397
]
Andrew Purtell edited comment on HBASE-4374 at 9/13/11 6:25 AM:
----------------------------------------------------------------
If we can get online schema edits into 0.92, at least metadata like HTD/HCD
attributes, then users can easily change the region size split threshold as
tables grow. Can add a ruby script helper for this purpose in bin or shell
support. Does not take away from talking up presplitting but provides a good
alternative if presplitting is not an option for whatever reason (e.g. keyspace
distribution not well known).
was (Author: apurtell):
If we can get online schema edits into 0.92, at least metadata like HTD/HCD
attributes, then users can easily change the split points as tables grow. Can
add a ruby script helper for this purpose in bin or shell support. Does not
take away from talking up presplitting but provides a good alternative if
presplitting is not an option for whatever reason (e.g. keyspace distribution
not well known).
> Up default regions size from 256M to 1G
> ---------------------------------------
>
> Key: HBASE-4374
> URL: https://issues.apache.org/jira/browse/HBASE-4374
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Priority: Blocker
> Fix For: 0.92.0
>
>
> HBASE-4365 has some discussion of why we default for a table should tend to
> fewer bigger regions. It doesn't look like this issue will be done for 0.92.
> For 0.92, lets up default region size from 256M to 1G and talk up pre-split
> on table creation in manual.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
