[
https://issues.apache.org/jira/browse/AVRO-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891715#action_12891715
]
Doug Cutting commented on AVRO-495:
-----------------------------------
So, here's a concrete proposal: at the start of a protocol definition we permit
imports of three different forms, one for an idl file, one for a JSON protocol
file and one for a JSON schema file:
{code}
protocol Sample {
import idl "../../share/authenticate.avdl";
import protocol "../../share/authorize.avpr";
import schema "datetime.avsc";
...
}
{code}
Quoted paths would be relative to the IDL file being processed. Subsequently,
in a separate issue, we might search other directories, and add a syntax for
"system" imports, perhaps something like:
{code}
import schema <date.avsc>
{code}
> Avro IDL should support includes
> --------------------------------
>
> Key: AVRO-495
> URL: https://issues.apache.org/jira/browse/AVRO-495
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.3.1
> Reporter: Eric Evans
>
> includes would be a nice feature for Avro IDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
