hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11804) POC Hadoop Client w/o transitive dependencies
Date Tue, 01 Nov 2016 18:42:58 GMT

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

Sangjin Lee commented on HADOOP-11804:

Thanks for the work [~busbey]! I just did a quick test with the latest patch.

One high level concern is in terms of maintaining dependencies in the pom's. If a developer
adds a new dependency to a module, how would that propagate to these client pom's? Would he/she
need to add it to these client pom's for the most part? It wasn't entirely clear to me what
that cost of maintenance is. If that is the only way to keep it clean, that's OK. But it would
be great if that cost is kept to a minimum.

The patch indeed does not apply for me via plain {{git apply}}: it breaks with {{hadoop-client/pom.xml}}
and {{hadoop-maven-plugins/pom.xml}}. I did {{git apply --reject HADOOP-11804.1.patch}}.

Once I fixed the git apply issues, I did {{mvn clean install package -Pdist -DskipTests -Dmaven.javadoc.skip}}
and it fails right away:
[ERROR]   The project org.apache.hadoop:hadoop-client-minicluster:3.0.0-alpha2-SNAPSHOT (/Users/sjlee/git/hadoop-trunk/hadoop-client-modules/hadoop-client-minicluster/pom.xml)
has 1 error
[ERROR]     'dependencies.dependency.version' for org.mortbay.jetty:jetty:jar is missing.
@ line 266, column 17

I got past it by providing a version for this (chose 6.1.26).

The build still fails with a couple of duplicate classes issues. One is what Andrew reported
above. Another is duplicate jetty classes.
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.BanDuplicateClasses failed with message:
Duplicate classes found:

  Found in:
  Duplicate classes:

Was there a significant difficulty in handing the timeline service v.2? Is it just the number
of new dependencies we’re pulling in or the fact that there is a HBase dependency?

Regarding the logging libraries, I agree we probably want to exclude them. Things like log4j
properties and the way slf4j works can cause issues down the road if shaded.

> POC Hadoop Client w/o transitive dependencies
> ---------------------------------------------
>                 Key: HADOOP-11804
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11804
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>         Attachments: HADOOP-11804.1.patch, HADOOP-11804.2.patch, HADOOP-11804.3.patch,
> make a hadoop-client-api and hadoop-client-runtime that i.e. HBase can use to talk with
a Hadoop cluster without seeing any of the implementation dependencies.
> see proposal on parent for details.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message