Extend AVRO schema evolution rules

[jonsnowseven]

Hello.

I would like to extend the AVRO schema evolution rules to additionally to the default validation (in)validate the following change in a field: {“type”: “long”} -> {"type": {“type”: “long”, “logicalType”: “timestamp-millis”}}. AVRO itself allows this but on our use-case, we don't want it.

I noticed that we can customize Avro SerDe but I don't know exactly what I need to implement and provide it to Apicurio Registry.

Can anyone help please?
Thank you.

[EricWittmann]

Hi @jonsnowseven sorry for the late reply on this. We're working on a release. :)

There is currently no way to contribute custom rules to extend compatibility. Compatibility is currently checked primarily on the server, when schemas are registered. We don't have a feature that allows customization.

You could convert this discussion into a feature request issue in GitHub for the apicurio-registry project though!