mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MRUNIT-157) allow null keys and values as output, expected output
Date Fri, 01 Mar 2013 13:17:13 GMT

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

Brock Noland updated MRUNIT-157:
--------------------------------

    Priority: Critical  (was: Blocker)
    
> allow null keys and values as output, expected output
> -----------------------------------------------------
>
>                 Key: MRUNIT-157
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-157
>             Project: MRUnit
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Carlos Espinoza
>            Assignee: Jim Donofrio
>            Priority: Critical
>             Fix For: 1.0.0
>
>
> from comments at the end of MRUNIT-66:
> Hadoop allows null keys and values, when not used as intermediate keys,values between
mappers and reducers. MRUnit should also allow allow null keys and values as output and expected
output. The Serialization class will need to be modified to not try to copy null's into the
output, expected output

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

Mime
View raw message