[
https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778997#action_12778997
]
Owen O'Malley commented on HDFS-641:
------------------------------------
*Sigh* I apologize for not closing the loop on the complaints before committing
this. It had been so long since I started the process that I lost track that
you still weren't happy with the solution.
Cycles in the dependency graph make everything harder. Until we get the
interfaces locked down more and Common becomes more stable, there will be
cross-project commits. While that is true, we need all 3 trunks (common, hdfs,
and mapreduce) to depend on the current SNAPSHOT of each other. Otherwise, a
change a common will break all of them. Using a fixed version of mapreduce for
HDFS testing wouldn't work because that fixed version would become broken. In
short, we would need to depend on a specific SNAPSHOT version of mapreduce.
When would that be updated? Who would update it?
The majority of the move is about the tools and benchmarks using HDFS and
MapReduce that are better served being in MapReduce. Some of the the tests
should be recoded without MapReduce and pushed back into HDFS. However, most of
the tests are the distributed equivalent of the tests still in HDFS and aren't
that badly placed in MapReduce.
Having a strict build order without cycles is a huge win, especially for
automated build systems like Hudson running CI builds for us. With HADOOP-5107,
we no longer need to check in jar files. That makes life far easier for
developers. Automated CI builds are big part of it.
> 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.
