[
https://issues.apache.org/jira/browse/HBASE-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-7412:
-------------------------------
Status: Patch Available (was: Open)
Attached patch v2. In this patch, if the value (max file size, or mem flush
size) is not set, returns -1 instead of the default value. So the client can
decide what to do. If we return the default value, it is hard to tell if the
value is really set to the default value or not.
If the value is set to the default value, but it is configured to a different
value in hbase-site.xml, the existing code will use that value in the
hbase-site.xml. With the patch, the value set for the table will be used (in
this case, the default value).
> 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, trunk-7412_v2.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
