[
https://issues.apache.org/jira/browse/AVRO-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764532#comment-17764532
]
ASF subversion and git services commented on AVRO-530:
------------------------------------------------------
Commit c3b31f6ccff4bffd96af1543164412beb900c92b in avro's branch
refs/heads/dependabot/maven/lang/java/io.netty-netty-bom-4.1.97.Final from
Christophe Le Saec
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c3b31f6cc ]
AVRO-530: Allow recursive types in protocol (#1768)
* AVRO-530 recursives types in protocol
> allow for mutual recursion in type definitions
> ----------------------------------------------
>
> Key: AVRO-530
> URL: https://issues.apache.org/jira/browse/AVRO-530
> Project: Apache Avro
> Issue Type: Improvement
> Components: spec
> Affects Versions: 1.3.2
> Reporter: Jeff Hodges
> Assignee: Christophe Le Saec
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Suppose you have these two types in your protocol:
> {code}
> {"name": "User", "type": "record", "fields": [{"name": "current_status",
> "type": "Status"}]}
> {"name": "Status", "type": "record", "fields": [{"name": "author", "type":
> "User"}]}
> {code}
> This will raise an error! The current workaround is to define one of them at
> their first usage. Like:
> {code}
> {"name": "User", "type": "record", "fields": [{"name": "current_status",
> "type": {"name": "Status", "type": "record", "fields": [.. lots of fields
> ...]}]}
> {code}
> But this is incredibly unwieldy. It would be really nice for the spec to
> require all the parsers to allow for mutual recursion, instead. It could be
> done by implementing a two-pass parser. One pass to acquire names referenced,
> and a second to fill in those names with their appropriate references.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
