In MAPREDUCE-1126 you suggested that we add these methods directly to WritableSerialization and AvroSerialization. We could move them into the MR project proper, though I don't know that o.a.h.m.lib.input makes much sense as a destination – these methods are configuring the intermediate data types, not the input types.
For future-proofing purposes: I anticipate that for
MAPREDUCE-815, we'll also need to add related methods to set the serialization metadata maps for the final output key and value types. (a la JobConf.setOutputKeyClass()). It would be nice if the output type configuration and the intermediate type configuration remained "close together" (e.g., in the same package).
Should we add a new package that contains a configuration API around serializers? e.g. o.a.h.m.lib.serialization or o.a.h.m.lib.types