You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Tim Perkins (JIRA)" <ji...@apache.org> on 2019/03/30 22:11:00 UTC

[jira] [Updated] (AVRO-2199) Validate that field defaults have the correct type

     [ https://issues.apache.org/jira/browse/AVRO-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Perkins updated AVRO-2199:
------------------------------
    Fix Version/s: 1.9.0
       Attachment: AVRO-2199.patch
           Status: Patch Available  (was: Open)

>  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)