Deserialization fails with ccompat/v7 API when using Apicurio Serializer 3.1.0

[Rahul-20]

Hi @EricWittmann,

I’m currently retesting the issue reported in #6640 and wanted to clarify the expected behaviour based on my observations below.

Steps to Reproduce

1. Serialise a protobuf message using the Apicurio Serializer 3.1.0 version with the following flags to make it compatible with the Confluent library:
   SerdeConfig.SEND_TYPE_REF = "false",
   SerdeConfig.SEND_INDEXES = "true"

2. Attempt to deserialize the message using Apicurio, but configure the registry URL to use ccompat/v7.

Observed Behavior:
Deserialization fails when using the ccompat/v7 API.
However, deserialization succeeds when using the v3 API.

Could you please confirm whether deserialization using the ccompat/v7 endpoint is expected to be supported in this scenario?

[EricWittmann]

If you are using Apicurio Serializers/Deserializers you MUST configure them to use the Core API. They do not work with the ccompat API. The ccompat API is only for compatibility with Confluent tools. So any tools that require the Confluent API should be configured to use the ccompat API.