Subject not found about avrora HOT 4 CLOSED

Solved.

The registry in this platform is not Confluent's. Turns out new subjects need an explicit creation step in this one.

from avrora.

@fxn Glad that issue resolved. Do anything that this library can improve emerge? I'm not quite sure that I understand about an explicit step. Technically the subject is registered every time you encode the payload

from avrora.

I don't have enough perspective to suggest an improvement.

The first time you encode, the library performs a POST to register the schema, and subsequent encodings use the returned ID. Using Confluent's registry, if the subject does not exist, it is created when you POST. This has worked flawlessly in development using the Docker image confluentinc/cp-schema-registry.

However, when I started deploying this project to company servers, that initial POST was failing with

{:error, %{"error_code" => 40401, "message" => "Subject not found"}}

Turns out, this platform is actually using https://github.com/hortonworks/registry, and this registry does not auto create subjects. If the subject is new, you need to manually create the subject first with a POST to

/api/v1/schemaregistry/schemas

that has a series of special attributes like schemaGroup.

Once the new subject is created, then Avrora's POSTs to register versions work just fine as usual.

from avrora.

@fxn Thanks for the insights, I've checked the registry you are using, what I can say – they have 2 different endpoints for new and existing schema manipulations: create schema and update schema.

This is an additional and a bit different behavior that I need to explore in the future. I have a plan to support out-of-band behavior and currently already have a few issues and ideas to implement, like:

• Schema registration task
• Read-only behavior for registry storage (out-of-band)

And seems it will be cool to implement support for a new registry (I guess)

from avrora.