wrote: > I'm working on migrating an internally developed serialization format to Avro. > In the process, there have been many cases where I made a mistake migrating > the schema (I've automated it), and then avro cries that a record I'm trying > to serialize doesn't match the schema. Generally, the error it gives doesn't > help find the actual issue, and for a big enough record finding the issue can > be tedious. > > I've thought about making a tool which, given the schema and the record would > tell you what the issue is, but I'm wondering if this already exists? I > suppose the error message could also include this information... > > Thanks > Jon --B_3448100533_9145349 Content-type: text/html; charset="US-ASCII" Content-transfer-encoding: quoted-printable

Try GenericRecordBuilde= r.

For the Specific API, there are builders = that will not let you construct an object that can not be serialized.

<= div>The Generic API should have the same thing, but I am not 100% sure the b= uilder there covers it.

I have always avoided using= any API that allows me to create an object that is unsafe to serialize sinc= e finding out at serialization time is a huge pain (and in my case, is often= on a separate thread from the place it was created).

On 4/4/13 6:58 AM, "Jonathan C= oveney" <jcoveney@gmail.com> w= rote:

<= div>
I'm working on migrating an internally developed serializ= ation format to Avro. In the process, there have been many cases where I mad= e a mistake migrating the schema (I've automated it), and then avro cries th= at a record I'm trying to serialize doesn't match the schema. Generally, the error it gives doesn't help find = the actual issue, and for a big enough record finding the issue can be tedio= us.

I've thought about making a tool which, given the schema and the record wou= ld tell you what the issue is, but I'm wondering if this already exists? I s= uppose the error message could also include this information...

Thanks
Jon

--B_3448100533_9145349--