[
https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779005#action_12779005
]
Doug Cutting commented on HDFS-641:
-----------------------------------
> Sharad/Hemant/Dhruba/Me all were either -1 or not +1 for the fix that got
> committed.
No clear -1 votes were cast, but It's still not too late. If a committer feels
this is wrong, it can be reverted and discussed further. We require one +1
review before commits, which I don't see above, and, even then, committers
should still be able to veto and revert a change for the first few days after
it's been committed in case they didn't have a chance to review it before it
was committed.
> 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.
