[
https://issues.apache.org/jira/browse/HBASE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007026#comment-13007026
]
stack commented on HBASE-2170:
------------------------------
@Lars I don't think we'll be bringing asynchbase into core (BenoƮt won't let
us! Ahead of his refusal, he makes a good argument that it makes no sense
bringing it in). I think a separate maven module would be necessary making the
separation, probably the first step, or rather second step. The first step is
finding an advocate willing to take on this knarly issue.
There would be a few advantages to extracting the client. Way back when the
gumgum lads tried to make the client/server go against Interfaces only.
Currently our Interface has zk pollution, a pollution that has gotten worse
since gumgum boys last tried it. This might be the third step we'd take on
making a separate client lib.
> hbase lightweight client library as a distribution
> ---------------------------------------------------
>
> Key: HBASE-2170
> URL: https://issues.apache.org/jira/browse/HBASE-2170
> Project: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira