[
https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094755#comment-16094755
]
ASF subversion and git services commented on AVRO-1485:
-------------------------------------------------------
Commit 7941a14223c329d7bc0e62bf7e59db276a925539 in avro's branch
refs/heads/branch-1.7 from [~nkollar]
[ https://git-wip-us.apache.org/repos/asf?p=avro.git;h=7941a14 ]
AVRO-1485: Specification says Record field type can be record name but
implementation allows any named type.
(cherry picked from commit 21b369895cc6826b862605796bc35704bd142841)
(cherry picked from commit ea472174c7c1281270d7b071a76ee308bc772189)
> 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)
