[AVRO-3917] [Rust] Field aliases are not taken into account when calculating schema compatibility

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.12.0, 1.11.4
• Labels: pull-request-available
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Marcos Schroh
• Created: 11/Dec/23 12:54
• Updated: 18/Dec/23 18:18
• Resolved: 12/Dec/23 10:20

Description

When calculating the schema compatibility field aliases are not taken into account to calculate the end result, for example:

The compatibility result for following schemas (writer schema_v1 and reader schema_v2) must be Ok(()), but it is not the case

 

let schema_v1 = Schema::parse_str(r#"
{

    "type": "record",
    "name": "Conference",
    "namespace": "advdaba",
     "fields": [
         {"type": "string", "name": "name"},
         {"type": "long", "name": "time"}
     ]

}"#)?;

let schema_v2 = Schema::parse_str(r#"
{
    "type": "record",
    "name": "Conference",
    "namespace": "advdaba",
     "fields": [
         {"type": "string", "name": "name"},
         {"type": "long", "name": "date", "aliases" : [ "time" ]}
     ]
}"#)?;

 
Then the compatibility gives the following error

assert!(SchemaCompatibility::can_read(&schema_v1, &schema_v2).is_err());

// Incompatible schemata! Field 'date' in reader schema must have a default value"

The error must not happen because date has the time alias

Issue Links

• links to: GitHub Pull Request #2633