Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <697639065.1253899696854.JavaMail.jira@brutus>
Date: Fri, 25 Sep 2009 10:28:16 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-641) Move all of the benchmarks and tests
 that depend on mapreduce to mapreduce
In-Reply-To: <319045692.1253642416192.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759636#action_12759636 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-641:
---------------------------------------------

{quote}
A similar problem happens with your proposal too no? Let's say someone changes some functionality in common/hdfs and do not update the corresponding the test-case in mapreduce(for e.g., org.apache.hadoop.security.authorize.TestServiceLevelAuthorization.java). This will NOT be detected till mapreduce is built. If we talk of Hudson, then this won't happen till a mapreduce build is triggered by Hudson, which will be only when some other mapreduce patch is committed.
{quote}

That's correct but this is no cycle if we remove the dependence from hdfs to mapreduce.

BTW, tests like TestServiceLevelAuthorization should be spitted into individual hdfs and mapreduce tests.

> Move all of the benchmarks and tests that depend on mapreduce to mapreduce
> --------------------------------------------------------------------------
>
>                 Key: HDFS-641
>                 URL: https://issues.apache.org/jira/browse/HDFS-641
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.20.2
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.21.0
>
>
> Currently, we have a bad cycle where to build hdfs you need to test mapreduce and iterate once. This is broken.

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