Schema Registry & Discovery API SSL client authentication and enabling the Authorisation Code flow with PKCE. Two of them we would like to highlight to this blog. Either it was the responsibility of the producer or the stream team to make this schema available somewhere in the organizationįor the 2021.2 release we have worked on multiple security improvements. However, in previous versions of our platform there was not really a way to exchange schemas to use in the producer or consumer application(s). As producers and consumers we can now use the same schema in our applications to produce to the applicable topic.

This way you can test a schema in the development environment, before promoting it to the acceptance or production environment. Moreover, we allow you to upload different versions of schema’s, and use different schema versions in different environments. This way, you prepare your Avro schema to be selected as soon as you create a topic. Through the Self-Service interface you can already upload an Avro schema with a particular version and a description. Apache Avro is an example of a schema format which can be used. Every message contains a reference to the schema which is stored externally in a schema registry. The producer uses the schema to serialize and the consumer to deserialize messages. A schema contains information about the fields which are present in messages on the topic. When producers and consumers interact through a topic, it is important that both parties speak the same language. Read more about bug fixes and improvements in the release notes which can be found in our online documentation.

A Distributor caching issue causing some offsets not to be distributed correctly, potentially causing duplicate consumption of messages.

Race condition in the AvroDeserializer used in Stream Browse & search in multi tenant deployments.

Windows line endings support for certificate and schema files.As long as no topic exists in the environment, you are free to edit whatever you want. That’s why we added an extra check to prevent this from happening. However, changing the environment name after you have created topics in those environment could lead to very weird behaviour. This helps you to test-drive your apps on topics without having to create them with different names and such. From this release we also worked to prevent erroneous situations.Īs you know you can use our Self-Service interface to define environments which are mapped to a physical Kafka cluster.

Free download Imagine 1.3.0