[
https://issues.apache.org/jira/browse/MRUNIT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431993#comment-13431993
]
Dave Beech commented on MRUNIT-135:
-----------------------------------
Hi Tarun - Although TableMapper only has two type args, it extends
Mapper<ImmutableBytesWritable, Result, KEYOUT, VALUEOUT> which has 4. So it
should still work. IdentityMapper also has two type args and works fine.
You do get this kind of error if you are accidentally mixing old and new apis,
e.g. trying to pass a new API org.apache.hadoop.mapreduce.Mapper to the old API
org.apache.hadoop.mrunit.MapDriver. Can you confirm this isn't the case?
> How to test a TableMapper<Text,Text> with mrunit.
> -------------------------------------------------
>
> Key: MRUNIT-135
> URL: https://issues.apache.org/jira/browse/MRUNIT-135
> Project: MRUnit
> Issue Type: Question
> Affects Versions: 0.9.0
> Reporter: Tarun Adiwal
> Priority: Blocker
> Fix For: 0.9.1
>
>
> Currently I am writing a unit test case using mrunit. My mapper is a
> TableMapper<Text,Text> and I am getting compilation error while setting my
> mapper to MapReducedriver/MapDriver.
> The MapDriver requires four argument <KEYIN,VALUEIN,KEYOUT,VALUEOUT> but my
> TableMapper has only two arguments <KEYOUT,VALUEOUT> and hence when setting
> mapper to MapDriver I am getting compilation error.
> Is there any way I can write testcase with TableMapper using mrunit?
> I am using mrunit-0.9.0.
> Kind Regards,
> Tarun
--
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