[ 
https://issues.apache.org/jira/browse/AVRO-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806195#comment-16806195
 ] 

ASF subversion and git services commented on AVRO-2199:
-------------------------------------------------------

Commit 392c761952ec7f679b29ae28129403ea8cf307ea in avro's branch 
refs/heads/master from Tim Perkins
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=392c761 ]

AVRO-2199: Validate that field defaults have the correct type  (#497)

* AVRO-2199:  Validate that field defaults have the correct type

* AVRO-2199: Code review comments

* AVRO-2199: Make it configurable whether field default validation is enforced 
for Ruby


>  Validate that field defaults have the correct type
> ---------------------------------------------------
>
>                 Key: AVRO-2199
>                 URL: https://issues.apache.org/jira/browse/AVRO-2199
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: ruby
>    Affects Versions: 1.8.2
>            Reporter: Daniel Orner
>            Priority: Minor
>             Fix For: 1.9.0
>
>         Attachments: AVRO-2199.patch
>
>
> 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)

Reply via email to