[
https://issues.apache.org/jira/browse/HBASE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2036:
-------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Release Note: HBaseConfiguration as an object is now deprecated. Use
HBaseConfiguration.create to make an Hadoop Configuration populated with hbase
config. from here on out.
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed TRUNK. Thanks for the patch Enis. It was a bug in how Merge was
using Configurable interface that was causing the test failure. Let us know if
anything else we can do to help out your effort.
> Use Configuration instead of HBaseConfiguration
> ------------------------------------------------
>
> Key: HBASE-2036
> URL: https://issues.apache.org/jira/browse/HBASE-2036
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Enis Soztutar
> Fix For: 0.21.0
>
> Attachments: hconf.patch, hconf_v1.patch
>
>
> HBaseConfiguration extends Configuration but does not add any functionality
> to it. The only function is hashCode() which really should be refactored into
> Hadoop Configuration.
> I think in all the places(especially in the client side) HBase methods and
> classes should accept Configuration rather than HBaseConfiguration. The
> creation of the configuration with the right files (hbase-site and
> hbase-default) should not be encapsulated in a private method, but in a
> public static one.
> The issues has arisen in our nutch+hbase patch for which we include both
> nutch configuration and hbase configurations. Moreover people may want to
> include separate project-specific configuration files to their configurations
> without the need to be dependent on the HBaseConfiguration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
