[
https://issues.apache.org/jira/browse/HBASE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868341#action_12868341
]
stack commented on HBASE-2170:
------------------------------
An argument for making hbase-common, hbase-server, and hbase-client not really
mentioned above is that if we adopt these componentizations, and follow through
with them, we'll end up with a software base that is more easy to maintain than
the current hairball we currently have.
I'm good w/ going this route. What gives me pain is that we'd have to do it
using mvn modules. We have the opportunity just now of making our mvn build
simple having ejected all contribs; we could undo module support. But module
support I think is required to do the above componentization.
> hbase lightweight client library as a distribution
> ---------------------------------------------------
>
> Key: HBASE-2170
> URL: https://issues.apache.org/jira/browse/HBASE-2170
> Project: Hadoop HBase
> Issue Type: Wish
> Reporter: Kay Kay
> Attachments: jdepend-report.html
>
>
> As a wish - it would be nice to have a hbase client library (subset of the
> current hbase distribution) that needs to be present at the hbase client
> level to interact with the master/region servers.
> From an app integration - users of hbase can just link against the client
> library as opposed to getting the entire library to link against.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
