[jira] [Updated] (MRUNIT-66) null input checks and behavior on no input to a driver are inconsistent

["Jim Donofrio (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRUNIT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Donofrio updated MRUNIT-66:
-------------------------------

    Summary: null input checks and behavior on no input to a driver are inconsistent  (was: null input checks are inconsistent in at least the MapDriver class)
    
> 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: 1.0.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira