You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/11/05 01:58:00 UTC

[jira] [Resolved] (HBASE-21434) [hbase-connectors] Cleanup of kafka dependencies; clarify hadoop version

     [ https://issues.apache.org/jira/browse/HBASE-21434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-21434.
---------------------------
      Resolution: Fixed
    Release Note: Cleaned up kafka submodule dependencies. Added used dependencies to pom and removed the unused. Depends explicitly on hadoop2. No messing w/ hadoop3 versions.

Merged.

> [hbase-connectors] Cleanup of kafka dependencies; clarify hadoop version
> ------------------------------------------------------------------------
>
>                 Key: HBASE-21434
>                 URL: https://issues.apache.org/jira/browse/HBASE-21434
>             Project: HBase
>          Issue Type: Bug
>          Components: hbase-connectors, kafka
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: connector-1.0.0
>
>
> Running mvn dependency:analyze against hbase-connectors turned up a bunch of unused dependencies as wall as dependencies we rely on but don't mention in pom.
> I tried to do hadoop2/hadoop3 profiles in kafka module but figured makes no sense since it only references hadoop-common just to get at Configuration; made hadoop2 dependency explicit (Tried to do hadoop2/hadoop3 in top-level pom but won't be relevant always and its messy at the top-level around the hbase-hadoop2-compat module.... For another time).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)