[
https://issues.apache.org/jira/browse/MRUNIT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426923#comment-13426923
]
Bertrand Dechoux commented on MRUNIT-64:
----------------------------------------
Did the patch get already applied? I am doing a first patch for MRUNIT-125. As
the result the input setters will be the same whether it is the mapred or the
mapreduce API. However, the inputs are not checked the same way for both APIs.
For me it would mean that multiple inputs are not handled the same way for both
APIs. That's why I am asking here.
Eg MapDriver
-> mapred
if (inputKey == null || inputVal == null) {
throw new IllegalStateException("No input was provided");
}
-> mapreduce
if (inputKey != null && inputVal != null) {
setInput(inputKey, inputVal);
}
if (inputs == null || inputs.size() == 0) {
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: New Feature
> 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
