avro-dev mailing list archives

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

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

Jeff Hammerbacher commented on AVRO-659:
----------------------------------------

Handling imports with Avro IDL is a separate problem from the one I'm trying to describe (poorly).
Once Avro IDL outputs a .avsc, that .avsc file needs to be stored somewhere and that location
needs to be communicated to the code that will be using the schema. You could just inline
the JSON into your code during the Avro IDL compile stage, but some developers might prefer
to keep the file separate. If the file is separate, we need a standard way for code that uses
the file to locate it.

Does that make sense?

> 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.


Mime
View raw message