[
https://issues.apache.org/jira/browse/AVRO-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082486#comment-13082486
]
Bill Graham commented on AVRO-872:
----------------------------------
Yes, the former parsing approach will work with the current patch. We'd just
need to add the convenience method to do
{{Schema schema = parser.getSchemaByName("Player");}}
(Or maybe {{getType}} aligns more with the existing API?) This would allow the
caller to load a number of files and then fetch the schema(s) they're
interested in, without necessarily knowing which file contained it. They'd
still need to be sure to parse in reverse-dependent order.
Thanks for the pointer re Protocol parsing, that worked.
> Allow interdependancies across IDL schema imports
> -------------------------------------------------
>
> Key: AVRO-872
> URL: https://issues.apache.org/jira/browse/AVRO-872
> Project: Avro
> Issue Type: Improvement
> Reporter: Bill Graham
> Assignee: Doug Cutting
> Attachments: AVRO-872.patch, AVRO-872.patch
>
>
> This currently doesn't work because Player depends on Position, but it should:
> {noformat}
> $ cat position.avsc
> {"type":"enum", "name": "Position", "namespace": "avro.examples.baseball",
> "symbols": ["P", "C", "B1", "B2", "B3", "SS", "LF", "CF", "RF", "DH"]
> }
> $ cat player.avsc
> {"type":"record", "name":"Player", "namespace": "avro.examples.baseball",
> "fields": [
> {"name": "number", "type": "int"},
> {"name": "first_name", "type": "string"},
> {"name": "last_name", "type": "string"},
> {"name": "position", "type": {"type": "array", "items":
> "avro.examples.baseball.Position"} }
> ]
> }
> $ cat baseball.avdl
> @namespace("avro.examples.baseball")
> protocol Baseball {
> import schema "position.avsc";
> import schema "player.avsc";
> }
> $ java -jar avro-tools-1.5.1.jar idl baseball.avdl baseball.avpr
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
