Resolved
This incident has been resolved
Identified
We identified the root cause of the error. When messages are produced via Aiven Kafka REST and validated by Aiven Schema Registry, applying the standard convention became mandatory with Karapace 3.7.0. Previously created schemas applying the standard naming convention f"{topic_name}-key" and f"{topic_name}-value" are not affected by the error.
We are now actively working on a Karapace code change to mitigate the potential regression on user applications involving non-conventional schema names. Meanwhile, the workaround is to publish a message including its schema definition so it gets automatically re-created, or to duplicate previously existing schemas to conventional names f"{topic_name}-key" and f"{topic_name}-value". Please reach out to Aiven Support for any further need for assistance.
We apologise for the inconvenience caused by this issue. We will provide a further update on regular basis.
Investigating
Following our last production update of Kafka REST API, we identified an issue preventing Kafka REST producers from publishing messages related to certain schema naming conventions. We are currently working on a fix and will continue to update the progress here.
The workaround would be to publish a message including schema definitions so they get re-created, or duplicate previously existing schemas to conventional names f"{topic_name}-key" and f"{topic_name}-value".
We apologise for the inconvenience caused by this issue. We are currently working on a fix and will update on regular basis.