[
https://issues.apache.org/jira/browse/AVRO-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043387#comment-17043387
]
Ryan Skraba commented on AVRO-2760:
-----------------------------------
Hello! Unfortunately it's a bit unclear from your description - is this a
schema resolution problem (using both schema1 and schema2 to read the data)?
Could it be related to the nested namespace fixes from AVRO-2663, or AVRO-1646
(recent changes to nested records that should only appear in 1.9.2)?
A bit more detail on reproducing would be useful, and if possible, a failing
unit test would be a great way to clarify.
> Avro 1.9.2 - Reading nested AVRO created by earlier versions is failing
> -----------------------------------------------------------------------
>
> Key: AVRO-2760
> URL: https://issues.apache.org/jira/browse/AVRO-2760
> Project: Apache Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.9.1, 1.9.2
> Reporter: Indrani Boppana
> Priority: Critical
>
> Say we have a schema with nestedStructure, for business reasons the schema
> structure was left intact but the namespaces have changed.
> schema1 - namespace1
> schema2 - namespace2
>
> We have data generated with 1.8.2, with schema1. lets call it Data1.
> When we read the Data1 as SpecificRecord with schema2 using 1.9.x avro
> library. We did notice that when its getting deserialized the top level
> structures are getting interpreted fine, but nested record structures are
> getting interpreted as namespace1 classes instead of namespace2. And thats
> causing Runtime class cast exceptions.
> When we read that Data1 as SpecificRecord with schema2 using 1.8.2 avro
> library. We did notice that when its getting deserialized the nested record
> structures are getting interpreted as namespace2 classes as expected... no
> issues.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
