[
https://issues.apache.org/jira/browse/AVRO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045575#comment-13045575
]
Scott Carey commented on AVRO-837:
----------------------------------
I have been working on changes to the Java library that are eerily similar in
intent, and somewhat in implementation (functional decomposition, flexible fine
grained configurable mapping of Avro to types). I have not been actively
working on these for the last ~4 weeks but expect to put the first patches into
JIRA soon since I have time to work on it again.
Prior Avro 1.6, comparing our approaches and insights would be useful and might
lead to improvements for both (though the languages differ significantly at the
detail level). I'll be having a deeper look at this later, but since I haven't
done much C programming in the last 7 years its a little slow to digest :)
> 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
>
> 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
