hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-641) Move all of the benchmarks and tests that depend on mapreduce to mapreduce
Date Fri, 25 Sep 2009 17:28:16 GMT

    [ 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:

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.

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

> 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.

View raw message