You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mrunit.apache.org by "Jim Donofrio (Updated) (JIRA)" <ji...@apache.org> on 2012/02/26 10:12:48 UTC

[jira] [Updated] (MRUNIT-66) null input checks are inconsistent in at least the MapDriver class

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

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

    Description: 
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

  was: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)

    
> null input checks are inconsistent in at least the MapDriver class
> ------------------------------------------------------------------
>
>                 Key: MRUNIT-66
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-66
>             Project: MRUnit
>          Issue Type: Improvement
>            Reporter: Jim Donofrio
>            Priority: Minor
>
> 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