Failing to load schema with references

[bbrcan]

Hi there,

I have the following enum called Status:

{
  "schema": {
    "type": "enum",
    "namespace": "test",
    "name": "Status",
    "symbols": ["Pending", "Enroute", "Arrive", "Complete"]
  }
}

And the following schema called Route:

{
  "schema": {
    "type": "record",
    "namespace": "test",
    "name": "Route",
    "fields": [
      {
        "name": "orgId",
        "type": "string"
      },
      {
        "name": "status",
        "type": "Status"
      }
    ]
  },
  "references": [
    {
      "name": "test.Status",
      "subject": "Status",
      "version": 1
    }
  ]
}

When I try to load the Route schema via either GetSchemaByVersion or GetSchema, I get back:

schema registry error: Record "test.Route" field 2 ought to be valid Avro named type: unknown type name: "Status"

Note I am using sc.CodecCreationEnabled(true). Happy to disable this but then I'm not quite sure how I'd load the codec with the references.

I've also tried referencing the Status type as test.Status in the Route schema, to no avail.

Can you shed any light on why this might be occurring? Thank you

Using srclient 0.7.0, Golang 1.23

[bbrcan]

For those interested I've managed to get around this by the following:

• Setting sc.CodecCreationEnabled(false) (this is default anyway)
• For each reference, download the schema (you may have to do this recursively). Then use a regex or string replacement to substitute that into the parent schema.
• Build the codec using your new "flattened" schema which now doesn't contain any references.

[AtakanColak]

Hi @bbrcan, thank you for raising this issue. It seems to be related to the behaviour around codec, and the underlying goavro package doesn't seem to have any documentation for reference types.

[gabrielclimb]

The problem with this approach is you end with a schema like this

{
  "id" : "26f883a2-64ba-4033-804d-496f6ad0396b",
  "transaction_reference_number" : {
    "string" : "ref-001"
  },
  "is_pre" : {
    "boolean" : true
  },
  "entry_mode" : {
      "co.entities.reference.name" : "bvalue"
    }
}

which is a nightmare to solve