You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Douglas Creager (JIRA)" <ji...@apache.org> on 2011/07/14 04:41:59 UTC

[jira] [Resolved] (AVRO-837) New Avro value interface

     [ https://issues.apache.org/jira/browse/AVRO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Douglas Creager resolved AVRO-837.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

I've gone ahead and committed this to SVN on the 1.6.0 trunk branch.  All of the existing test cases pass, so this should be backwards-compatible with 1.5-and-earlier code.  And the new avro_value_t API is pretty stable at this point.

Scott, your idea about comparing how we're doing this in the Java and C libraries is a good one.  I can make any tweaks that come up from that before we cut a 1.6.0 release.

> New Avro value interface
> ------------------------
>
>                 Key: AVRO-837
>                 URL: https://issues.apache.org/jira/browse/AVRO-837
>             Project: Avro
>          Issue Type: New Feature
>          Components: c
>    Affects Versions: 1.6.0
>            Reporter: Douglas Creager
>            Assignee: Douglas Creager
>             Fix For: 1.6.0
>
>
> I've been working on a new interface for representing Avro values.  The new interface supports custom implementations, which allows you to directly use instances of existing C types as Avro values.  It also includes a "generic" implementation of the interface that's much faster and more space efficient than the old avro_datum_t class.  Lastly, the interface includes support for zero-copy getters and setters for bytes, string, and fixed values.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira