Using Confluent Schema Registry since v0.25.0: Magic byte and Schema ID not removed from beginning of JSON value

[Rob3681]

Starting with version 0.25.0 (and also 0.25.1), the bytes at positions 0-4 (magic byte + schema ID) are not removed from the beginning of a record value that was produced using a schema from the Confluent Schema Registry. This means that a JSON value is not displayed formatted, but instead as a one-liner. Furthermore, the data cannot be copied so easily with CTRL+A + CTRL+C; an empty string is written to the clipboard.

I use the following configuration:

akhq:
  connections:
    test:
      properties:
        bootstrap.servers: abc.europe-west3.gcp.confluent.cloud:9092
        security.protocol: SASL_SSL
        sasl.mechanism: PLAIN
        sasl.jaas.config: >-
          org.apache.kafka.common.security.plain.PlainLoginModule required
          username="KAFKA-API-KEY"
          password="KAFKA-API-SECRET";
      schema-registry:
        url: https://xyz.europe-west3.gcp.confluent.cloud
        type: confluent
        basic-auth-username: SR-API-KEY
        basic-auth-password: SR-API-SECRET

Access to the schema registry generally works. It is recognized that the value was produced using a schema from the Confluent Schema Registry, I can display the schema content and I can also specify the schema when producing a message.

With the identical configuration, the problem does not occur in version 0.24.0:

[AlexisSouquiere]

Strange issue. I'm also using a Confluent registry with version 0.25.1 in my company and we don't have such issue.
Can you paste the entire application.yml ?

[Rob3681]

Do you use JSON schemas or AVRO schemas? I only have the problem with JSON schemas. The problem does not occur with AVRO schemas.

The configuration that I wrote in the issue is the entire content of my application.yaml.

[AlexisSouquiere]

Ok that's probably why I don't have the issue. We are only using Avro. I will investigate