[AVRO-3898] [rust] compatibility fails with different namespaces

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.11.3
• Fix Version/s: 1.12.0, 1.11.4
• Component/s: rust
• Labels: pull-request-available rust

Language

Rust

• Assignee: Martin Tzvetanov Grigorov
• Reporter: Santiago Fraire Willemoes
• Created: 01/Nov/23 14:24
• Updated: 02/Nov/23 12:41
• Resolved: 02/Nov/23 12:38

Description

Current behavior

SchemaCompatibility does not work properly when `namespace` is present.

The following schemas are `FORWARD` compatible.

use avro_rs::{Schema, schema_compatibility::SchemaCompatibility};

let schema_1 = Schema::parse_str(r#"{
  "type": "record",
  "name": "Statistics",
  "fields": [
    { "name": "succes", "type": "int" },
    { "name": "fail", "type": "int" },
    { "name": "time", "type": "string" },
    { "name": "max", "type": "int", "default": 0 }
  ]
}#").unwrap();

let schema_2 = Schema::parse_str(r#"{
  "type": "record",
  "name": "Statistics",
  "fields": [
    { "name": "succes", "type": "int" },
    { "name": "fail", "type": "int" },
    { "name": "time", "type": "string" },
    { "name": "average", "type": "int"}
  ]
}#").unwrap();

When using `SchemaCompatibility::can_read(...)` the result is `true`:

assert_eq!(true, SchemaCompatibility::can_read(&schema_1, &schema_2););

However, when the `namespace` is added then the result is `false`

let schema_3 = Schema::parse_str(r#"{
  "type": "record",
  "name": "Statistics",
  "namespace": "my.namespace"
  "fields": [
    { "name": "succes", "type": "int" },
    { "name": "fail", "type": "int" },
    { "name": "time", "type": "string" },
    { "name": "max", "type": "int", "default": 0 }
  ]
}#").unwrap();

assert_eq!(false, SchemaCompatibility::can_read(&schema_3, &schema_2););

Desired behavior
Namespace should not affect compatibility

Notes

• My team is going to provide a PR soon to fix it

Issue Links

• links to: GitHub Pull Request #2574