[jira] Commented: (HBASE-2036) Use Configuration instead of HBaseConfiguration

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-2036:
------------------------------

I'm not so sure hashcode in HBC is a good idea.  Its up in the air at the moment.  It'll probably be removed.

If we used plain Configuration Enis, how would we ensure that hbase-*.xml had been read into the Configuration?   The public static method you allude to above would be where?

What if we kept HBC and just changed methods so they took a Configuration, not necessarily an HBC?  Would that work?

Thanks.



> 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
>
> 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.