You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous version of the library, calling ProtobufDeserializer.__call__ with ctx=None worked. With the new version it fails with an AttributeError, around here
I think this was introduced by this recent change #1852
There is a work around, consisting of passing asubject.name.strategy that ignores the context:
I would argue that the code should be able to handle a null ctx, without having to change the config..
In particular in the context of a ProtobufDeserializer that doesn't have a schema registry set (and is using schema on read). Because in this case, the subject is not used, and therefore the ctx is not needed.
AvroDeserializer behaves in the same way unfortunately... Since it (this behavior) wasn't present in previous releases shouldn't be it treated as a breaking change?
I mean, changing parameter (moving it from optional into required) is a breaking change...
The
ctx
argument inProtobufDeserializer
is marked as Optional.confluent-kafka-python/src/confluent_kafka/schema_registry/protobuf.py
Line 815 in 3f40f19
In previous version of the library, calling
ProtobufDeserializer.__call__
withctx=None
worked. With the new version it fails with anAttributeError
, around hereI think this was introduced by this recent change #1852
There is a work around, consisting of passing a
subject.name.strategy
that ignores the context:I would argue that the code should be able to handle a null ctx, without having to change the config..
In particular in the context of a
ProtobufDeserializer
that doesn't have a schema registry set (and is using schema on read). Because in this case, the subject is not used, and therefore the ctx is not needed.Steps to reproduce:
The text was updated successfully, but these errors were encountered: