any reason to add direct multiple inputs support for avro?

[tazan007 <ta...@gmail.com>]

Hi guys, I am contemplating working on adapting multiple inputs to work
with AvroInputFormat to directly tie a key/value schema to a particular
input path.

Something like this in AvroJob:

  public static void addInputPath(Job job, Path src,
                                  Class<? extends InputFormat>
inputFormatClass,
                                  Schema inputKeySchema,
                                  Schema inputValueSchema
                                  )

I know that people are just creating unions to overcome the lack of direct
multiple inputs support for avro input format.  The question is, would the
above really be beneficial over the current approach of creating schema
unions?

Thanks,
Hiral