hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7412) Fix how HTableDescriptor handles default max file size and flush size
Date Wed, 26 Dec 2012 19:36:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539648#comment-13539648

Elliott Clark commented on HBASE-7412:

* Should we just make HTableDescriptor take in a Conf in the constructor ?  Then everything
that relies on region.getTableDescriptor won't have any code changes.
* It looks like this will cause a few javadoc errors (Hadoop qa missed them but it would catch
them now I think).  
* I don't think that the forced un-boxing on Long is needed for the two return Long.valueOf.
> Fix how HTableDescriptor handles default max file size and flush size
> ---------------------------------------------------------------------
>                 Key: HBASE-7412
>                 URL: https://issues.apache.org/jira/browse/HBASE-7412
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.96.0, 0.94.4
>         Attachments: 0.94-7412.patch, trunk-7412.patch
> If the region flush size is not set in the table, IncreasingToUpperBoundRegionSplitPolicy
will most likely always use the default value: 128MB, even if the flush size is set to a different
value in hbase-site.xml.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message