[AVRO-3900] Permissiveness in schema namespaces for rust SDK?

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.3
• Fix Version/s: 1.12.0, 1.11.4
• Component/s: rust
• Labels: pull-request-available
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Jon Slusher
• Created: 07/Nov/23 21:02
• Updated: 01/Feb/24 14:17
• Resolved: 25/Jan/24 07:22

Description

We have an Avro schema registry that has schema with hyphens in some of the namespaces. These schema were created by our Debezium connectors. We have Python consumers that are able to use them without an issue, but we're trying to write a consumer in Rust and it appears that the Avro SDK for rust doesn't support this permissiveness.

 

Here's an example of one of the schema created by our Debezium connectors: 

 

{
  "type": "record",
  "name": "Envelope",
  "namespace": "debezium.example-connector-20231005.database.my_table",
  "fields": [
    {
      "name": "before",
      "type": [
        "null",
        {
          "type": "record",
          "name": "Value",
          "fields": [
            {
              "name": "id",
              "type": "int"
            },
            {
              "name": "uid",
              "type": {
                "type": "long",
                "connect.default": 0
              },
              "default": 0
            },
...

 

If that schema is allowed in our Avro Schema Registry I would think that it should be allowed by any consumer trying to use it. 

 

I opened an [issue in the rust schema converter crate's repository|https://github.com/gklijs/schema_registry_converter/issues/100], and it appears that the problem is in the Avro SDK. 

Issue Links

• links to: GitHub Pull Request #2643