Grokbase Groups Avro user April 2013
Try GenericRecordBuilder.

For the Specific API, there are builders that will not let you construct an
object that can not be serialized.
The Generic API should have the same thing, but I am not 100% sure the
builder there covers it.

I have always avoided using any API that allows me to create an object that
is unsafe to serialize since finding out at serialization time is a huge
pain (and in my case, is often on a separate thread from the place it was
On 4/4/13 6:58 AM, "Jonathan Coveney" 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...


Search Discussions

Discussion Posts


Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 7 of 7 | next ›
Discussion Overview
groupuser @
postedApr 4, '13 at 1:58p
activeApr 6, '13 at 8:42p



site design / logo © 2021 Grokbase