hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12556) KafkaSink jar files are created but not copied to target dist
Date Wed, 23 Mar 2016 20:54:25 GMT

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

Allen Wittenauer commented on HADOOP-12556:

HADOOP-12857 as been committed.  I believe that effectively unblocks this patch, since it
would mean that the kafka jars would only be in the classpath if the user enables the hadoop-kafka
entry in hadoop-env.sh, as no remaining Hadoop code in trunk blindly adds all of the tools
lib to the classpath.

Let's verify that's the case and if [~stevel@apache.org] is amenable, this can get committed.

> KafkaSink jar files are created but not copied to target dist
> -------------------------------------------------------------
>                 Key: HADOOP-12556
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12556
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Babak Behzad
>            Assignee: Babak Behzad
>         Attachments: HADOOP-12556.patch
> There is a hadoop-kafka artifact missing from hadoop-tools-dist's pom.xml which was causing
the compiled Kafka jar files not to be copied to the target dist directory. The new patch
adds this in order to complete this fix.

This message was sent by Atlassian JIRA

View raw message