[
https://issues.apache.org/jira/browse/AVRO-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Orner updated AVRO-2199:
-------------------------------
Description:
Currently, on the master branch, when a schema is parsed, it is possible to
define a field with a type and a default of a totally different type. E.g. if
the field has type "string", the default can be set to "null".
I'd like to open a PR which will fix this by running the default through the
SchemaValidator whenever a new Field is created. See
[https://github.com/salsify/avro-patches/pull/16]
cc: [~tjwp]
was:
Currently, on the master branch, when a schema is parsed, it is possible to
define a field with a type and a default of a totally different type. E.g. if
the field has type "string", the default can be set to "null".
I'd like to open a PR which will fix this by running the default through the
SchemaValidator whenever a new Field is created. See
https://github.com/salsify/avro-patches/pull/16
> Validate that field defaults have the correct type
> ---------------------------------------------------
>
> Key: AVRO-2199
> URL: https://issues.apache.org/jira/browse/AVRO-2199
> Project: Avro
> Issue Type: Improvement
> Components: ruby
> Affects Versions: 1.8.2
> Reporter: Daniel Orner
> Priority: Major
>
> Currently, on the master branch, when a schema is parsed, it is possible to
> define a field with a type and a default of a totally different type. E.g. if
> the field has type "string", the default can be set to "null".
> I'd like to open a PR which will fix this by running the default through the
> SchemaValidator whenever a new Field is created. See
> [https://github.com/salsify/avro-patches/pull/16]
> cc: [~tjwp]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
