hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5107) split the core, hdfs, and mapred jars from each other and publish them independently to the Maven repository
Date Fri, 25 Sep 2009 06:58:16 GMT

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

Vinod K V commented on HADOOP-5107:
-----------------------------------

Looked at the patch overall and tested it. Works fine when connected.

One major point : the patch assumes upfront that the dependency order is common->hdfs->mapred.
There is another alternative : common->mapred and common->hdfs. In many local discussions,
I didn't hear one final conclusion regarding this. Please also see HDFS-641. The first approach
pushes some hdfs specific tests/benchmarks into mapred which may or may not be very correct.
The second one still leaves the location of these tests/benchmarks unanswered. What does the
community think about this? 

Your failures w.r.t run-test-hdfs-with-mr and others should be connected to the above point,
I guess.

> split the core, hdfs, and mapred jars from each other and publish them independently
to the Maven repository
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5107
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5107
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.20.0
>            Reporter: Owen O'Malley
>            Assignee: Giridharan Kesavan
>         Attachments: common-trunk-v1.patch, common-trunk-v4.patch, common-trunk.patch,
hadoop-hdfsd-v4.patch, hdfs-trunk-v1.patch, hdfs-trunk-v2.patch, hdfs-trunk.patch, mapred-trunk-v1.patch,
mapred-trunk-v2.patch, mapred-trunk-v3.patch, mapred-trunk-v4.patch, mapred-trunk-v5.patch,
mapreduce-trunk.patch
>
>
> I think to support splitting the projects, we should publish the jars for 0.20.0 as independent
jars to the Maven repository 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message