You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by "Prashant Kommireddi (JIRA)" <ji...@apache.org> on 2013/07/11 21:39:48 UTC
[jira] [Commented] (MRUNIT-157) allow null keys and values as
output, expected output
[ https://issues.apache.org/jira/browse/MRUNIT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706147#comment-13706147 ]
Prashant Kommireddi commented on MRUNIT-157:
--------------------------------------------
Hey guys - is this something that should be/will be fixed? We are moving from 0.20.1+152 to 1.0.0. Adding null as key worked in the former but throws a NPE in the latter version.
Is there a workaround? How are nulls handled?
> 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.1.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