Skip to content

[Bug]: Python SchemaRegistry is not properly populated when calling add #29975

@mlhamel

Description

@mlhamel

What happened?

In that #28169

The following change was introduced:

  def add(self, typing, schema):
    if not schema.id:
      self.by_id[schema.id] = (typing, schema)

I know the SCHEMA_REGISTRY is an internal service but we were using it in our tests and stopped working with the release of beam 2.51.

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3awaiting triagebugdone & doneIssue has been reviewed after it was closed for verification, followups, etc.python

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions