Support for schema evolution? about avrora HOT 5 CLOSED

Hey @coryodaniel and thanks for the report. May I ask you to describe the process which causes an issue with step-by-step instructions that I can reproduce it?

So far I understand that you have an empty registry and encode something with schema/v1 Avrora is registering it and encode the message, then you somehow change the schema (questions: where and how?) and Avrora is still using old schema/v1

May I ask you to clarify the moment of evolution of the schema?

1. Do you update the schema file? If yes, I think Avrora will not re-read it because it doesn't know that file is updated (if we are talking about the same running process) 🤔
2. Do you update the registry schema outside Avrora? If yes, Avrora will read the new registry schema if a global-naming cache is invalidated, but not a file.

Can you elaborate on that? I'm happy to help you with this issue 🤝

from avrora.

from avrora.

Ah, got it, then it's definitely an issue, that local schema file goes after the registry, it should be first especially on startup.

I will make this scenario locally and check that it will work correctly, also will what I can do with logging of dropped fields (agree that will be great to know that they were dropped)

from avrora.

Awesome, much appreciated!

from avrora.

@coryodaniel Hey, I've a PR with fix #30 I plan to release it today/tomorrow. Any feedback is appreciated (if you have one) 🤝

from avrora.