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
I'm testing out Apicurio using apicurio/apicurio-registry-mem:2.2.2.Final docker image and testing confluent python and dotnet packages using protobuf. When I try to use proto schema I'm receiving status code 422.
It seems like there is an inconsistency how proto schemas represented between the confluent schema-registry and apicurio. After debugging the issue a bit more confluent packages use Protobuf base64 encoded format while apicurio expect the input being string and return "Failed to discover artifact type from content. (HTTP status code 422, SR code 42201)" error.
Hello,
I'm testing out Apicurio using apicurio/apicurio-registry-mem:2.2.2.Final docker image and testing confluent python and dotnet packages using protobuf. When I try to use proto schema I'm receiving status code 422.
It seems like there is an inconsistency how proto schemas represented between the confluent schema-registry and apicurio. After debugging the issue a bit more confluent packages use Protobuf base64 encoded format while apicurio expect the input being string and return "Failed to discover artifact type from content. (HTTP status code 422, SR code 42201)" error.
Python package:
Endpoint used :
http://localhost:8080/apis/ccompat/v6
Failing request:
POST
http://localhost:8080/apis/ccompat/v6/subjects/test-value/versions
Request content:
Example reproducer following confluent python example - I have a similar one for dotnet as well if that helps.
user.proto:
On python side this is where the conversion happening before sending the schema to the registry:
https://github.com/confluentinc/confluent-kafka-python/blob/e7e066120f05ca6f9c37b18d77f974f1a6cad222/src/confluent_kafka/schema_registry/protobuf.py#L290
The equivalent happening on dotnet side as well when sending protobuf schemas to the registry.
The text was updated successfully, but these errors were encountered: