hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13517) Publish a client artifact with shaded dependencies
Date Tue, 21 Apr 2015 19:09:59 GMT

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

Elliott Clark commented on HBASE-13517:
---------------------------------------

bq.I'm generally of the opinion that you should relocate absolutely everything you can.
K, working on it.

bq.Is Hadoop's Configuration really in our API?
Yeah return values for HBaseConfigurations and as function parameters for Connection creation
and MR job submission.

> Publish a client artifact with shaded dependencies
> --------------------------------------------------
>
>                 Key: HBASE-13517
>                 URL: https://issues.apache.org/jira/browse/HBASE-13517
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.1.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-13517-v1.patch, HBASE-13517-v2.patch, HBASE-13517.patch
>
>
> Guava's moved on. Hadoop has not.
> Jackson moves whenever it feels like it.
> Protobuf moves with breaking point changes.
> While shading all of the time would break people that require the transitive dependencies
for MR or other things. Lets provide an artifact with our dependencies shaded. Then users
can have the choice to use the shaded version or the non-shaded version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message