[
https://issues.apache.org/jira/browse/AVRO-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872343#comment-16872343
]
ASF subversion and git services commented on AVRO-2440:
-------------------------------------------------------
Commit c3e79364b905c5414e65118ad218850ec76f204c in avro's branch
refs/heads/branch-1.9 from Oscar WvH-K
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c3e7936 ]
AVRO-2440: Decode messages by their write schema
This implements AVRO-2440 by allowing a null value for the readSchema
field in the BinaryMessageDecoder. It is interpreted as "no preference",
and makes the decoder use the write schema of an incoming buffer as its
read schema.
(cherry picked from commit 371e22468baa045b5eb5f1e05ee716d3996f520e)
> Allow BinaryMessageDecoder to read (generic) records with the same schema
> they were written with.
> -------------------------------------------------------------------------------------------------
>
> Key: AVRO-2440
> URL: https://issues.apache.org/jira/browse/AVRO-2440
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Reporter: Oscar Westra van Holthe - Kind
> Priority: Minor
> Fix For: 1.10.0
>
>
> At work we have a use case to read Avro records from Kafka, and to write them
> to one of several BigQuery tables (based on compatibility). This means that
> there is no single schema (with all data) that is compatible with all records
> we'll be reading.
> In order to allow this, we'd like to be able to use the BinaryMessageDecoder
> without any read schema, and have it use the write schema of each record as
> the read schema for that record.
> -Pull request will follow.-
> Pull request submitted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
