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 (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/26 03:02:26 UTC

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

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

Jim Donofrio resolved MRUNIT-66.
--------------------------------

    Resolution: Fixed

added new ArgumentChecker class in internal.util with returnNonNull method which returns the input if not null or throws an exception if null
also added returnNonNull for lists to check that all entries in a list are not null
internal package will be for classes that have to be public to be used by the api but should not be relied upon by users, MRUNIT-92 will handle not generating javadoc for internal classes
added returnNonNull calls to all public api methods
simplified Pair implementation since null's are no longer allowed, null's dont make sense in Pair since no mapper/reducer will input/output null

committed in 1305185
                
> 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