[
https://issues.apache.org/jira/browse/HBASE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842326#action_12842326
]
dhruba borthakur commented on HBASE-2170:
-----------------------------------------
It appears that from a build perspective (inefficient maven dependencies, etc,
etc) you would want to split hbase into multiple jars. But from a deployment &
operation perspective, it is a nightmare. Can somebody please enumerate which
jars are currently required by a hbase client application and also enumerate
which jars will be needed by after this patch?
Also, can somebody who is *using* hbase vouch for the fact that the splitting
of jars is helpful?
The analogy I draw is that the hadoop libraries are the same for the hadoop
clients as well as servers. I have found it to be great help for operation
purposes: there is lesser chance of mixing up different incompatible versions.
> 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
>
> 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.
