[
https://issues.apache.org/jira/browse/MRUNIT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971691#comment-13971691
]
Jason E Tedor commented on MRUNIT-205:
--------------------------------------
All tests that existed at the time I cloned the repository were unchanged and
continue to pass.
Regarding incompatibilities, it depends on what you mean.
There is a single (but very minor) public change. Previously,
{{o.a.h.mrunit.TestDriver}} had five generic parameters, two of which were
unused in {{TestDriver}}. I removed these two unused parameters from
{{TestDriver}} and obviously changed the extending classes (e.g.
{{o.a.h.mrunit.MapDriverBase}}) to no longer use these generic parameters in
their {{extends}} clauses. However, the type parameter list of the extending
classes did not change.
Therefore, the only public change is that anyone that was extending
{{TestDriver}} will have to remove these two unused parameters from the
{{extends}} clauses of their extending classes.
> Add support for MultipleInputs
> ------------------------------
>
> Key: MRUNIT-205
> URL: https://issues.apache.org/jira/browse/MRUNIT-205
> Project: MRUnit
> Issue Type: New Feature
> Reporter: Jason E Tedor
> Assignee: Jason E Tedor
> Attachments: MRUNIT-205.patch
>
>
> Some MapReduce jobs have multiple input sources that can even feed different
> Mapper implementations within the same job.
> MRUnit does not have a driver that natively supports testing these types of
> jobs.
> Note that this is not the same as MRUNIT-64. However, there are comments in
> that ticket that adding such support could be a good feature.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
