bq. context.write(hbaseKey, put); //Exception here
I am not mrunit expert. But as long as you call the following method prior
to the above method invocation, you should be able to proceed:
conf.setStrings("io.serializations", conf.get("io.serializations"),
MutationSerialization.class.getName(), ResultSerialization.class
.getName(),
KeyValueSerialization.class.getName());
Cheers
On Sun, Nov 2, 2014 at 2:24 PM, Sean Busbey <bus...@cloudera.com> wrote:
> On Sun, Nov 2, 2014 at 4:11 PM, Serega Sheypak <serega.shey...@gmail.com>
> wrote:
>
> > Sean, I've started to catch that serialization problem on unit-test level
> > while using mrunit.
> > I don't see any possibility to call
> > HFileOutputFormat.configureIncrementalLoad
> > before mrunit mocking stuff.
> > I was workngi w/o any problem in 0.94 :)
> >
> >
> >
> Ah. Well, that sounds like a bug in MRUnit for dealing with HBase 0.96+.
>
> As Ted mentioned, you'll have more luck on the mrunit mailing list for
> figuring that bit out.
>
> --
> Sean
>
