[
https://issues.apache.org/jira/browse/HBASE-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272104#comment-13272104
]
Jesse Yates commented on HBASE-5976:
------------------------------------
Great breakdown Matt!
Yeah, it would be to ditch the current hbase-core in favor of hbase-common.
My preference for hbase-common is just because I think its going to be harder
than we think to pull server classes out (having tried it once, it is pure
misery). True, that in theory the server classes will likely be a large chunk
of code, but I think we are going to end up with doing a lot this piecemeal, a
couple server classes at a time. Since the server and client packages depend on
common, HMaster and HRegion/HRegionServer seem like good initial candidates for
the move.
Stack had previously mentioned that he'd rather wait on doing a client module
until we rewrite the client, which seems a reasonable request (but who has the
time?). This means we will likely take a while to get the hbase-client package
out (especially since things are very entangled for between the client and
server).
-1 hbase-hbase (and transitively hbase-core since its essentially also a
holding name) and hbase-server for the above reasons.
It would be great to do all this refactoring and client rewrite in 0.96, but
I'm not holding my breath. In the meantime, common is a pretty standard name
that everyone can use and won't hose downstream projects too much in terms of
maven dependency naming (much simpler profiles will be possible, in contrast to
the mess that we have with the different hadoop profiles).
> Initial module naming
> ---------------------
>
> Key: HBASE-5976
> URL: https://issues.apache.org/jira/browse/HBASE-5976
> Project: HBase
> Issue Type: Brainstorming
> Components: build
> Affects Versions: 0.96.0
> Reporter: Jesse Yates
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> There is currently a lot of discussion around the 'right' name for the
> initial module that will host all the code in the primary modularization of
> hbase. The current contenders are:
> * hbase-core
> * hbase-common
> * hbase-server
> * hbase-bucket
> * hbase-hbase
> Let's duke it out and pick the best, while keeping in mind that this module
> will *not* remain the sole module going forward, but is merely the precursor
> Timeline to close this issue is the day before the code gets committed.
> Source:
> http://search-hadoop.com/m/pwi1t1e9K0R/modularizing+trunk&subj=modularizing+trunk
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
