You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v7.7.2 of the AvroConverter returns different serialization output depending on the orders that fields are declared in the input schema. As a result, when serializing data using a schema from the schema registry different serialized output is produced for the same input value when using two syntactically equivalent schemas.
To better illustrate the issue, I've created PR #3375 with a test case that highlights this behavior.
Expected Behavior
When serializing data using a schema from the schema registry, the order that fields are declared in the input schema should not affect the output from AvroConverter.fromConnectData(...).
Current Behavior
When serializing data using a schema from the schema registry, the order that fields are declared in the input schema affects the output from AvroConverter.fromConnectData(...).
Steps to Reproduce
This PR #3375 contains the below test case which highlights the issue.
v7.7.2 of the
AvroConverter
returns different serialization output depending on the orders that fields are declared in the input schema. As a result, when serializing data using a schema from the schema registry different serialized output is produced for the same input value when using two syntactically equivalent schemas.To better illustrate the issue, I've created PR #3375 with a test case that highlights this behavior.
Expected Behavior
When serializing data using a schema from the schema registry, the order that fields are declared in the input schema should not affect the output from
AvroConverter.fromConnectData(...)
.Current Behavior
When serializing data using a schema from the schema registry, the order that fields are declared in the input schema affects the output from
AvroConverter.fromConnectData(...)
.Steps to Reproduce
This PR #3375 contains the below test case which highlights the issue.
The text was updated successfully, but these errors were encountered: