hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15762) Consider hbase-client to be shaded by default in 2.0
Date Tue, 03 May 2016 22:02:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269698#comment-15269698

Enis Soztutar commented on HBASE-15762:

bq. What gets used server side
The hbase-client module and all of HTable / Connection, etc. If hbase-server depends on hbase-client
which is shaded, and hbase-server is not, we might be using two different versions of the
same third party classes from the server side. 
bq. How about we rename the current hbase-client module something else and then place the
shaded client at those maven coordinates?
I think that might work. Before proceeding with this jira however, we should make sure that
the shaded client is not causing any regression in terms of the API surface. 

> Consider hbase-client to be shaded by default in 2.0 
> -----------------------------------------------------
>                 Key: HBASE-15762
>                 URL: https://issues.apache.org/jira/browse/HBASE-15762
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>             Fix For: 2.0.0
> We have hbase-client and hbase-shaded-client for branch-1. For 2.0, I think we should
just get rid of the hbase-shaded-client and only have hbase-client which is shaded by default.
No need to have un-shaded client thus preventing applications to shoot themselves in the foot.

> One caveat though is that hbase-client is used in the server side. 

This message was sent by Atlassian JIRA

View raw message