[
https://issues.apache.org/jira/browse/HBASE-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550996#comment-13550996
]
Anoop Sam John commented on HBASE-5148:
---------------------------------------
Mikael Sitruk
Where the config param "hbase.hregion.majorcompaction" is used, we are 1st
checking whether this is added at the table level. If not we take the server
level value configured in the xml file.
HTableDescriptor#getValue() is just a getter on the POJO. It should return the
value which is set on it (if set something). IMO it no need to fetch the data
from the config xml. When this value is used we need to consider the value from
HTableDescriptor or config..
I think this is not a valid bug and can be closed.
> Compaction property at the server level are not propagated at the table level.
> ------------------------------------------------------------------------------
>
> Key: HBASE-5148
> URL: https://issues.apache.org/jira/browse/HBASE-5148
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 0.90.1
> Reporter: Mikael Sitruk
>
> In case you do not override compaction parameter on the table/cf level, the
> values returned by the table descriptor will not reflect the value configured
> in the cluster.
> For example - let assume you disabled major compaction by setting
> "hbase.hregion.majorcompaction" in the config to "0", prior starting the
> cluster. Let also assume that you have a table that in which you didn't set
> at all this parameter.
> Then invoking
> HTableDescriptor hTableDescriptor =
> conn.getHTableDescriptor(Bytes.toBytes("my table"));
> hTableDescriptor.getValue("hbase.hregion.majorcompaction")
> should return the cluster property (currently returns the default, ignoring
> the cluster prop.)
--
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
