Skip to content
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

Doesn't work with schema registry as source for writer schema #41

Closed
blatyo opened this issue Aug 13, 2020 · 2 comments
Closed

Doesn't work with schema registry as source for writer schema #41

blatyo opened this issue Aug 13, 2020 · 2 comments
Labels
feature Something new to build

Comments

@blatyo
Copy link

blatyo commented Aug 13, 2020

Expected

When I encode data with Avrora.encode(data, schema_name: @schema, format: :registry), I successfully get back the encoded data.

Actual

Whenever I encode data, I get back {:error, :enoent}. this line tries to read a file that doesn't exist yet. This project seems to assume that the writing schema will always be available locally. For our projects we occasionally have multiple writers of the same schema, so our schema files live independently of the specific projects.

The 0.9.x line seems to behave as expected.

@blatyo blatyo changed the title Doesn't work with schema registry Doesn't work with schema registry as source for writer schema Aug 13, 2020
@Strech
Copy link
Owner

Strech commented Aug 13, 2020

@blatyo Hey, thanks for the issue. I have a plan to support out-of-band registration and pure reader without any attempt to write the schema. I will do it right after I finish with #39. As a very rough ETA something in 1-1.5 weeks.

With 0.9.x was an issue when people were using reader/writer approach and schemas were never updated because were found in the registry.

The idea is to have an option to say read-only – always read from the registry and fail if not found. Sounds good?

@Strech
Copy link
Owner

Strech commented Sep 8, 2020

@blatyo Evening, I have some news. In Avrora 0.13 you can find a new configuration option registry_schemas_autoreg which can be set to false. It will prevent schemas from being registered and also read from the disk.

Release notes will come soon. Enjoy!

Closed #45

@Strech Strech closed this as completed Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new to build
Projects
None yet
Development

No branches or pull requests

2 participants