Koert Kuipers 2013-10-14, 04:20
Note that builders do supply defaults.
But that might not help you much here.
You might intersect your config json with the reader schema to determine
its implied writer schema.
On Oct 13, 2013 9:21 PM, "Koert Kuipers" <[EMAIL PROTECTED]> wrote:
> i am testing parsing a json string using a record class defined in an
> .avdl file.
> i was hoping that if a field in the record has a default value that it is
> not mandatory to provide it in the json. however i get an exception:
> org.apache.avro.AvroTypeException: Expected field name not found: test123
> i guess it was silly of me to expect this?
> are default values only used in schema resolution (so reader vs writer
> schema)? and in this case there is no writer schema, just json data i
> created and a reader schema, so the default values will not help me?
> too bad because this seemed like a really quick and convenient way to
> create configuration objects that can be instantiated from json, but
> without "optional" fields with default values it loses a lot of it power.
Harsh J 2013-10-20, 20:10