[
https://issues.apache.org/jira/browse/AVRO-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806214#comment-16806214
]
Hudson commented on AVRO-2199:
------------------------------
FAILURE: Integrated in Jenkins build AvroJava #632 (See
[https://builds.apache.org/job/AvroJava/632/])
AVRO-2199: Validate that field defaults have the correct type (#497) (fokko:
[https://github.com/apache/avro/commit/392c761952ec7f679b29ae28129403ea8cf307ea])
* (edit) lang/ruby/test/test_schema.rb
* (edit) lang/ruby/test/test_datafile.rb
* (edit) lang/ruby/.gitignore
* (edit) lang/ruby/lib/avro.rb
* (edit) lang/ruby/lib/avro/schema.rb
> 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
> Assignee: Tim Perkins
> 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)
