avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-659) Portable specification of the location of schema and protocol files
Date Wed, 08 Sep 2010 15:54:35 GMT

    [ https://issues.apache.org/jira/browse/AVRO-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907274#action_12907274

Doug Cutting commented on AVRO-659:

JSON-format schemas should be self-contained, since they must fully describe binary data.

However Avro IDL supports file inclusion (AVRO-495).  There was discussion in that issue about
searching a set of directories for included files.  I suggested we follow the C convention,
where double-quoted imports search the application's path and angle-bracketed imports search
a "system" path.  Would this address the need you describe?

> Portable specification of the location of schema and protocol files
> -------------------------------------------------------------------
>                 Key: AVRO-659
>                 URL: https://issues.apache.org/jira/browse/AVRO-659
>             Project: Avro
>          Issue Type: New Feature
>            Reporter: Jeff Hammerbacher
> Avro doesn't require code generation, which is great. However, if you want to use a protocol
or a schema, your code needs to know where to find it. When your code is ported to new systems,
the protocol or schema file must be placed in the same place as on the previous system for
things to work correctly.
> For importing modules in a portable fashion, Python provides a default set of places
it will look for modules and an environment variable called PYTHONPATH that programs can use
to override these defaults. It may be useful to explore similar constructs for Avro implementations
that don't do code generation. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message