Hi everyone,

I would like to override the input schema in AvroStorage to make a pig
script robust to schema evolution.  For example, suppose a new field is
added to an avro schema with a default value of null.  If the input to a
pig script using this field includes both old and new data, AvroStorage
will merge the input schemas from the old and new data.  However, if the
input includes only old data, the new schema will not be available to
AvroStorage and pig will fail to interpret the script with an error such
as "projected field [newField] does not exist in schema".  If AvroStorage
accepted an input schema, the script would be valid for both the new and
old data.  Is there any plan to implement this?

Thanks,
Steve

Reply via email to