[
https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758580#action_12758580
]
Vinod K V commented on HDFS-641:
--------------------------------
The current planned move is moving file-system specific tests which seem out of
place in mapreduce to me. If something changes in FS/HDFS, it looks very odd to
go and change the corresponding tests in mapred.
Why shouldn't HDFS tests and benchmarks just run with a specified version of
mapreduce instead of the latest version. This will remove the dependency of
building mapreduce every time a HDFS build is needed. If the tests/benchmarks
need something cutting edge in mapreduce, then the corresponding mapreduce jar
can be committed to HDFS at that point of time. Thoughts?
> 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.
