-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avrora schema registry registration fails due to Invalid payload format #135
Comments
Hey @EM51641 thanks for the kind words! Could you also tell me which version you use? I see the agent header as If it's the 0.25 I would suggest to upgrade to 0.29.1 |
This is working in 0.28.0, broken in 0.29.1 (and 0.29.0) It's this change: b11472d#diff-bf53ad6d056234d501d148f29e0f44f1b9884363abf9b4ec4dd25d640ebc8f67R74 Old code: PS: in my error report, I see this in the options param:
|
Yes, this is a bug, we are passing a map which is not matching with
Since we are mocking this function in tests that why were't able to catch it. Ideally we should mock the external call ( |
Fix was merged, but I would like to keep the issue to not forget and cover it with test |
Hi !
Amazing library but I just encountered an issue detailed underneath:
Description
When attempting to register an Avro schema with Schema Registry using Avrora, the registration fails with a
FunctionClauseError
. The error occurs because the payload being sent to the Schema Registry is a map when it should be a binary string.Current Behavior
The encode/decode test fails when trying to register the schema with the following error:
The payload is being sent as a map:
%{schema: "{\"namespace\":\"io.confluent\"..."}
when it should be a binary string.
Configuration
Schema Definition
Located at
priv/schemas/payment.avsc
:Confluent registry and kafka brokers config on a docker compose file.
The behavior tested is here:
This is a simple test case:
The text was updated successfully, but these errors were encountered: