mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Donofrio (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MRUNIT-66) null input checks are inconsistent in at least the MapDriver class
Date Sun, 26 Feb 2012 09:12:48 GMT

     [ 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

        

Mime
View raw message