[prev in list] [next in list] [prev in thread] [next in thread] 

List:       avro-dev
Subject:    [jira] [Assigned] (AVRO-1485) Specification says Record field type can be record name but implementa
From:       "Nandor Kollar (JIRA)" <jira () apache ! org>
Date:       2017-06-28 7:49:00
Message-ID: JIRA.12702327.1395209841000.122079.1498636140515 () Atlassian ! JIRA
[Download RAW message or body]


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

Nandor Kollar reassigned AVRO-1485:
-----------------------------------

    Assignee: Nandor Kollar

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


[prev in list] [next in list] [prev in thread] [next in thread]