You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
The text was updated successfully, but these errors were encountered:
Rob3681
changed the title
Using Confluent Schema Registry since v0.25.0: Magic byte and Schema ID not removed from beginning of value
Using Confluent Schema Registry since v0.25.0: Magic byte and Schema ID not removed from beginning of JSON value
Aug 1, 2024
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 ?
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:
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:
The text was updated successfully, but these errors were encountered: