avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francis Galiegue <fgalie...@gmail.com>
Subject Re: Experiment: a JSON Schema describing Avro schemas
Date Fri, 22 Feb 2013 22:04:44 GMT

On Fri, Feb 22, 2013 at 11:01 PM, Doug Cutting <cutting@apache.org> wrote:
> A few quick comments:
>  - properties besides those mentioned in the spec are permitted as
> metadata, e.g., {"type":"int", "java":"short"}.

By default, JSON Schema allows additional members, it will only forbid
them if additionalProperties is false (or constrain what they can be
if additionalProperties is a schema), so the question would rather be,
is there some scenarios where they are not allowed?

>  - a name can be prefixed by a namespace, e.g., {"type":"record",
> "name":"foo.Bar"}

Ah, OK. So you can have either a "full" name, a short name and a
namespace, or even a "full" name and a namespace?

>  - a schema can be the name of a schema defined earlier, e.g.
> {"type":"record", "name":"List", "fields":[{"name":"next",
> "type":[null, "List"]}]}

I don't believe the schema forbids that at this point but I guess I'll
have to check..


Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com

View raw message