[
https://issues.apache.org/jira/browse/AVRO-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303547#comment-17303547
]
Ryan Skraba commented on AVRO-2579:
-----------------------------------
Thanks for pointing this out -- it's just a bit too late to add a fix for
1.10.2. This looks like it could really catch someone off guard during a
migration...
On the positive side, we haven't seen reports of this breaking current user
code during a migration. It could be that ReflectData-generated schemas are
more "ephemeral" and it doesn't matter that field order changed, or it could be
that reader/writer schemas are taken into account, matching fields by name
during resolution.
Would you like to create a new JIRA to track this going forward?
> Test can fail with a different order of fields reflected
> --------------------------------------------------------
>
> Key: AVRO-2579
> URL: https://issues.apache.org/jira/browse/AVRO-2579
> Project: Apache Avro
> Issue Type: Bug
> Reporter: contextshuffling
> Priority: Minor
> Fix For: 1.10.0
>
>
> {{org.apache.avro.reflect.TestReflect#testAvroDoc compares the toString()
> version of the DocTest.class. It uses java.lang.Class.getDeclaredFields() to
> get the fields. However, this API does not guarantee the order of fields that
> gets returned. So test may fails due to a different order.}}
> {{https://github.com/contextshuffling/avro/blob/f9399780bfafd46bce1292da314f15b90f869572/lang/java/avro/src/test/java/org/apache/avro/reflect/TestReflect.java#L1319}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
