hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19399) Purge curator dependency from hbase-client
Date Sat, 02 Dec 2017 06:02:00 GMT

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

Duo Zhang commented on HBASE-19399:

Let me try to explain more.

For hbase-shaded, we have 4 modules, and hbase-shaded-check-invariants is only for checking
some rules so we only have 3 modules which we want to deploy, they are:

1. hbase-shaded-client
2. hbase-shaded-server
3. hbase-shaded-mapreduce

I believe they all do not need to depend on hbase-example, so once we purge the curator dependency
from hbase-client, then they will not depend on curator any more so we do not need to shade
curator and relocate it?

There is a relocation rule for curator in the pom of hbase-shaded


Or there are still transitive dependencies to curator? But I think that's the duty of the
one who depend on curator directly?


> Purge curator dependency from hbase-client
> ------------------------------------------
>                 Key: HBASE-19399
>                 URL: https://issues.apache.org/jira/browse/HBASE-19399
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, Zookeeper
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0-beta-1
>         Attachments: HBASE-19399-v1.patch, HBASE-19399.patch

This message was sent by Atlassian JIRA

View raw message