mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRUNIT-48) Test and Deprecate Driver.{*OutputFromString,*InputFromString} Methods
Date Sun, 26 Feb 2012 05:18:49 GMT

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

Brock Noland commented on MRUNIT-48:
------------------------------------

If a MRUnit test is using say LongWritable as the key, it's still possible to use the setOutputFromString
methods. The setOutputFromString methods have no way of knowing the key should be a LongWritable.
 As such, I think we should 1) deprecate these methods  2) write a unit test to confirm that
if the key is a non-Text type, MRUnit actually fails somewhere with a good error message.
                
> Test and Deprecate Driver.{*OutputFromString,*InputFromString} Methods
> ----------------------------------------------------------------------
>
>                 Key: MRUNIT-48
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-48
>             Project: MRUnit
>          Issue Type: Improvement
>            Reporter: Brock Noland
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> We should test a driver that only deals with, say LongWritable, to ensure the runTest()
method fails when we use the Driver.{*OutputFromString,*InputFromString} Methods.
> Additionally, I think we should deprecate these methods since they don't play well with
our generic interfaces.

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