[
https://issues.apache.org/jira/browse/AVRO-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Creager updated AVRO-863:
---------------------------------
Attachment: 0001-AVRO-863.-C-Schema-resolution-for-value-interface.patch
Here's an initial patch that implements this. I still need to add information
about using these new classes to the documentation.
In addition to implementing the new {{avro_resolved_writer_t}} and
{{avro_resolved_reader_t}} classes, this patch updates the existing datum I/O
code to use its value API wrapper.
> Schema resolution using new value interface
> -------------------------------------------
>
> Key: AVRO-863
> URL: https://issues.apache.org/jira/browse/AVRO-863
> Project: Avro
> Issue Type: New Feature
> Components: c
> Affects Versions: 1.6.0
> Reporter: Douglas Creager
> Assignee: Douglas Creager
> Attachments:
> 0001-AVRO-863.-C-Schema-resolution-for-value-interface.patch
>
>
> I mentioned this in one of my comments on AVRO-859, but hadn't opened an
> issue for it yet. I've been working on a schema resolution implementation
> for the new value interface in the C library (AVRO-837). It's similar in
> structure to the {{avro_resolver_t}} that I had written for the consumer
> interface. I'll describe in more detail in later comments (and in the
> documentation in the source tree), but there are two separate resolver
> classes for the value interface. Each is used to wrap an existing value
> instance, and to create a "view" of that value as if it were an instance of a
> different schema, and to use the Avro schema resolution rules to translate
> between the two schemas. The two classes are needed because the wrapped
> value might be on the "writer schema" side of the resolution, or on the
> "reader schema" side.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
