[HBASE-2036] Use Configuration instead of HBaseConfiguration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.90.0
• Hadoop Flags: Reviewed
• 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.
• Assignee: Unassigned
• Reporter: Enis Soztutar
• Created: 10/Dec/09 13:08
• Updated: 11/Oct/20 15:16
• Resolved: 31/Dec/09 20:45

Description

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.

Issue Links

• relates to: HBASE-25175 Remove the constructors of HBaseConfiguration