i have many avro files with similar data (same meaning, same type, etc.)
but different names for the fields.
can i create a reader schema that for each field that i am interested in
maps it to all the different possible fields in the files by using aliases,
and then run map-reduce over the files using this schema?
i am talking about tens of aliases per field, and this number will only
grow as more data comes in.
is this acceptible use of the alias concept, or is it abuse? and is the
alias implementation in avro efficient for such usage?