avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Gill (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.
Date Wed, 28 Jun 2017 14:16:00 GMT

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

John Gill commented on AVRO-1485:
---------------------------------

LGTM. Simple and clean

> Specification says Record field type can be record name but implementation allows any
named type.
> -------------------------------------------------------------------------------------------------
>
>                 Key: AVRO-1485
>                 URL: https://issues.apache.org/jira/browse/AVRO-1485
>             Project: Avro
>          Issue Type: Bug
>          Components: java, spec
>    Affects Versions: 1.7.6
>            Reporter: Sean Busbey
>            Assignee: Nandor Kollar
>         Attachments: AVRO-1485_1.patch
>
>
> The [specification for Record fields|http://avro.apache.org/docs/1.7.6/spec.html#schema_record]
says that the type is
> bq. A JSON object defining a schema, or a JSON string naming a record definition (required).
> AFAICT, the Java implementation allows for any [named type|http://avro.apache.org/docs/1.7.6/spec.html#Names].
> The specification should be updated to state any named type is allowed or the Java implementation
should restrict what can be used. The former seems less likely to disturb current users.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message