[
https://issues.apache.org/jira/browse/HBASE-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273861#comment-13273861
]
stack commented on HBASE-5976:
------------------------------
bq. @Matt: why the disposition to pulling up rather than pushing down?
Thinking on it, I think pulling up -- where up takes us toward more base types
and down takes us toward client facing APIs -- is viable in that I can see us
making headway extracting base types and utility out into coherent modules.
Going the other way, starting out at a base and then pulling classes won't
happen methinks. The master and the client and the regionserver packages all
reach into other. You won't be able to make modules of them (IMO). In fact, I
was thinking that the only way to go down would be by writing completely new
stuff; e.g. a new client (perhaps in org.apache.hbase package rather than
o.a.h.h to delineate it for sure a break w/ the past, or an hbase-server only
this server is server -- o.a.h.Server -- does regionserver and master roles
when called upon).
If this the case, hbase-common might be hard to work with. If we went w/
hbase-common, how would we make superior modules? What would we have to name
them: hbase-base? hbase-utils? hbase-base-types, hbase-foundation?
hbase-fundamentals?
hbase-cluster is a little awkward. I do appreciate that it is not 'loaded'
like core and common are though so its hard to peg which 'tier' it belongs to.
I would like to avoid our having core and common as over in hadoop. Its
strikes me as a failed modeling exercise whenever I trip over it.
> 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
