Jakub Senko

After additional investigation, I think the issue is related to this code https://github.com/Apicurio/apicurio-registry/blob/main/app/src/main/java/io/apicurio/registry/storage/impl/sql/AbstractSqlRegistryStorage.java#L1740 . When deleting a subject version, Registry has to determine what the next latest version is (e.g....

Confirmed this is happening on `snapshot` as well. Related to https://github.com/Apicurio/apicurio-registry/issues/2831

The [Confluent API documentation says](https://docs.confluent.io/platform/current/schema-registry/develop/api.html#delete--subjects-(string-%20subject)-versions-(versionId-%20version)): ``` version (versionId) – Version of the schema to be deleted. Valid values for versionId are between [1,2^31-1] or the string “latest”, which deletes the...

Wait, but they didn't reply, so how can you be sure it's not an issue on their side? I'd suggest you reopen the issue and depending on the answer, if...

Thank you!

Sorry, getting back to this, I'll create a fix to match the behavior of Confluent.

@mouadk Please check if the PR fixes your issue

@EricWittmann @carlesarnal WDYT about this change? It slightly changes the behavior of some REST API paths, so I think I need to at least add a feature flag. Should the...

Hi, Registry supports Confluent-compatible API, but you have to use this base path: `http://my-apicurio-service-registry/apis/ccompat/v6`. Try to change the URL configuration to that path. Edit: Sorry I missed that you are...

I would recommend to update to Registry 2.x if you can, it also supports Confluent-compatible API and contains a lot of new features and bug fixes.