Hi,
We got an issue with avro serialization/de-serialization when running a map-reduce job against avro data.  The input schema of the job is union of two schemas.  One of them is generated with Sqoop.  When avro calls to resolveUnion(Schema union, Object datum) in GenericData.java, it compares the names of component schemas of the union with that of the schema of datum.  However, the comparison alway fails because one of the name prepends with the corresponding namespace and the other not.  We have a workaround for this.  But we think this is a bug.  Can somebody verify this and fix it?  Thanks.          

Hi,

Can you file a JIRA for this at
https://issues.apache.org/jira/browse/AVRO with details on the version
you used and a short test case we can reproduce this with (or if not a
test case, even a few detailed steps to running into this would help)?

On Tue, Jan 31, 2012 at 7:19 AM, ey-chih chow <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We got an issue with avro serialization/de-serialization when running a
> map-reduce job against avro data.  The input schema of the job is union of
> two schemas.  One of them is generated with Sqoop.  When avro calls to
> resolveUnion(Schema union, Object datum) in GenericData.java, it compares
> the names of component schemas of the union with that of the schema of
> datum.  However, the comparison alway fails because one of the name prepends
> with the corresponding namespace and the other not.  We have a workaround
> for this.  But we think this is a bug.  Can somebody verify this and fix it?
>  Thanks.

--
Harsh J
Customer Ops. Engineer, Cloudera