[
https://issues.apache.org/jira/browse/HBASE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842469#action_12842469
]
Kay Kay commented on HBASE-2170:
--------------------------------
| btw, there's no reason not to produce a 'hbase-uber' artifact that combines
everything into one as there is now, that can be done with a fairly simple
assembly. For those that need/like having slimmer client libraries they can
still do that, those that feel safer with a fat jar, go right ahead.
Thanks Paul for the hint.
| +1 to Paul smith's proposal that we create a hbase-uher artifact. can this be
done as part of this patch Kay Kay?
Sure, Dhruba.
There will some be some work to move around some classes / methods to achieve
a decent separation between the client / common / server , before we venture
down the road of 3 separate artifacts. So yes - there will be an option for
the single jar as well, for distribution.
> 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.
