[
https://issues.apache.org/jira/browse/MRUNIT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424719#comment-13424719
]
Jim Donofrio commented on MRUNIT-64:
------------------------------------
I should have commented earlier but for all the deprecations you should put in
the javadoc why and what the user should use instead.
Why were the fluent methods only added to the mapreduce api?
Also why werent the same changes made to the mapred run methods as for
mapreduce?
Why in ReduceDriver does this not check for inputKey == null:
if (inputs.isEmpty()) {
throw new IllegalStateException("No input was provided");
}
> Multiple Input Key, Value Pairs should be supported
> ---------------------------------------------------
>
> Key: MRUNIT-64
> URL: https://issues.apache.org/jira/browse/MRUNIT-64
> Project: MRUnit
> Issue Type: Sub-task
> Affects Versions: 0.8.1
> Reporter: Brock Noland
> Assignee: James Kinley
> Fix For: 1.0.0
>
> Attachments: MRUNIT-64-v1.patch, MRUNIT-64.patch
>
>
> The comments on MRUNIT-14 brought up a great point. The API today only allows
> a single key value pair input. In many scenarios multiple inputs would be
> useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
