mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Ziemba (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRUNIT-157) allow null keys and values as output, expected output
Date Sun, 23 Aug 2015 08:37:46 GMT

    [ https://issues.apache.org/jira/browse/MRUNIT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708323#comment-14708323
] 

Dan Ziemba commented on MRUNIT-157:
-----------------------------------

I think you are supposed to use NullWritable.get() in your job instead of just null.

> 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.2.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message