[jira] [Updated] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

["Gabor Szadovszky (JIRA)" <ji...@apache.org>]

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

Gabor Szadovszky updated AVRO-1485:
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.3
                   1.9.0
                   1.7.8
           Status: Resolved  (was: Patch Available)

Checked with the doc generation on each branches. Seems that the -1 from the bot is really not relevant.

> 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
>             Fix For: 1.7.8, 1.9.0, 1.8.3
>
>         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)