[
https://issues.apache.org/jira/browse/MRUNIT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482293#comment-13482293
]
Jim Donofrio commented on MRUNIT-66:
------------------------------------
Yes this was an oversight on my part. The made reason I made this change was to
avoid people trying to set mappers to null and then wonder why they get a null
pointer later. I will create a new JIRA, MRUNIT-157, and allow null keys and
values except when testing keys out of the mapper with the MapReduceDriver,
right?
The bug in the 2nd comment is that we try to create copies of the output to add
to the list but dont try to handle null's correctly. I will also address this
in MRUNIT-157
> null input checks and behavior on no input to a driver are inconsistent
> -----------------------------------------------------------------------
>
> Key: MRUNIT-66
> URL: https://issues.apache.org/jira/browse/MRUNIT-66
> Project: MRUnit
> Issue Type: Improvement
> Affects Versions: 0.8.1
> Reporter: Jim Donofrio
> Assignee: Jim Donofrio
> Priority: Minor
> Fix For: 0.9.0
>
>
> the MapDriver class does not allow null input values if using setInput(Pair)
> but does allow null input if using setInputKey, setInputValue, or
> setInput(key, value)
> Also the MapDriver, ReduceDriver classes will throw null pointer exceptions
> with no input while the MapReduceDriver and Pipeline classes will just log
> warnings
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
