You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "mlhamel (via GitHub)" <gi...@apache.org> on 2024/01/10 21:19:00 UTC
[I] [Bug]: Python SchemaRegistry is not properly populated when calling `add` [beam]
mlhamel opened a new issue, #29975:
URL: https://github.com/apache/beam/issues/29975
### What happened?
In that https://github.com/apache/beam/pull/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
- [X] 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Python SchemaRegistry is not properly populated when calling `add` [beam]
Posted by "damccorm (via GitHub)" <gi...@apache.org>.
damccorm commented on issue #29975:
URL: https://github.com/apache/beam/issues/29975#issuecomment-1906290929
Hey @mlhamel as mentioned in https://github.com/apache/beam/blob/0a813b996572191bc179c724d3f31d535eb45e7d/sdks/python/apache_beam/typehints/schema_registry.py#L18 that code is intended for internal use only and does not have backwards compatibility guarantees. In general, you should not explicitly depend on its behavior unless you're ok taking on the risk of it changing
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Python SchemaRegistry is not properly populated when calling `add` [beam]
Posted by "damccorm (via GitHub)" <gi...@apache.org>.
damccorm closed issue #29975: [Bug]: Python SchemaRegistry is not properly populated when calling `add`
URL: https://github.com/apache/beam/issues/29975
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org