v3.3.2

What's Changed

• Add MI into the Products by @chathuranga-jayanath-99 in #87
• Update the kafka connector meta.json by @Bhashinee in #92
• Update meta.json & doc url by @arunans23 in #93
• Update meta information by @arunans23 in #96
• Update connector icon by @arunans23 in #97
• Update connector to enable a release workflow by @ChinthakaJ98 in #99
• Update connector metadata and fix build issues by @ChinthakaJ98 in #100
• Fix maven release issue by @ChinthakaJ98 in #101

New Contributors

• @chathuranga-jayanath-99 made their first contribution in #87
• @ChinthakaJ98 made their first contribution in #99

Full Changelog: v3.3.1...v3.3.2

3.3.1 Released!

This release adds support for UUID Logical Type validation.

3.3.0 Released!

This release adds the support to the following Apache Avro Logical Types.

• decimal
• uuid
• date
• time-millis
• time-micros
• timestamp-millis
• timestamp-micros
• local-timestamp-millis
• local-timestamp-micros

3.2.0 Released!

This release upgrades the Kafka client dependencies and Jackson dependencies. The recommended Kafka version is 2.8.1 from this release.

3.1.6 Released!

This release adds the following features.

1. Support SASL_SSL security protocol with the OAUTHBEARER mechanism.

• saslLoginCallbackHandlerClass - The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface.
• saslOauthbearerTokenEndpointUrl - The URL for the OAuth/OIDC identity provider
• saslOauthbearerScopeClaimName - (optional) The override name of the scope claim
• saslLoginConnectTimeout - (optional) The duration, in milliseconds, for HTTPS connect timeout
• saslLoginReadTimeout - (optional) The duration, in milliseconds, for HTTPS read timeout
• saslLoginRetryBackoff - (optional) The duration, in milliseconds, to wait between HTTPS call attempts
• saslLoginRetryBackoffMax - (optional) The maximum duration, in milliseconds, for HTTPS call attempts

2. Introduce the below properties.

• enableIdempotence - When set to ‘true’, the producer will ensure that exactly one copy of each message is written in the stream. If ‘false’, the producer retries due to broker failures, etc., and may write duplicates of the retried message in the stream.
• messageSendMaxRetries - This property will cause the producer to automatically retry a failed send request.
• reconnectBackoffMax - The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect.

3.1.5 Released!

This release fixes issues related to Content-Type and SASL Mechanism parameters in the publishMessage operation [1].

[1] Unable to save the “Content-Type” parameter and view “SASL Mechanism" parameter

3.1.4 Released!

This release add the following properties to the KafkaAvroSerializerConfigs.

• value.subject.name.strategy
• auto.register.schemas
• use.latest.version

Sample configuration to configure the properties

<kafkaTransport.init>
      <connectionType>kafka</connectionType>
      <keySerializerClass>io.confluent.kafka.serializers.KafkaAvroSerializer</keySerializerClass>
      <name>KAFKA_CONNECTION_1</name>
      <valueSerializerClass>io.confluent.kafka.serializers.KafkaAvroSerializer</valueSerializerClass>
      <bootstrapServers>localhost:9092</bootstrapServers>
      <poolingEnabled>false</poolingEnabled>
      <schemaRegistryUrl>http://localhost:8081</schemaRegistryUrl>
      <useLatestVersion>true</useLatestVersion>
      <autoRegisterSchemas>false</autoRegisterSchemas>
      <subjectNameStrategy>io.confluent.kafka.serializers.subject.RecordNameStrategy</subjectNameStrategy>
  </kafkaTransport.init>

2.0.10 Released!

Support configuring the message key dynamically by defining the key parameter.

3.1.3 Released!

This release adds the following features to Apache Avro type messages in the Kafka broker,

• Introduced another api capability to retrieve schema from confluent schema registry

• Earlier schema registry for both key and value could be retrieved from Kafka schema registry using Schema ID or hard coding the Schema inline. With this new improvement Schema can ve retrieved by providing Subject name (for key and value) and version (for key and value) following additional parameters can be provided in synapse configuration ,

        <valueSchemaSubject>transaction-value</valueSchemaSubject>
        <valueSchemaVersion>1</valueSchemaVersion>
        <valueSchemaSoftDeleted>true</valueSchemaSoftDeleted>
        <keySchemaSubject>transaction-value</keySchemaSubject>
        <keySchemaVersion>1</keySchemaVersion>
        <keySchemaSoftDeleted>true</keySchemaSoftDeleted>
  

3.1.2 Released!

This release adds the following features to Apache Avro type messages in the Kafka broker,

• Use default values defined in the schema when a field is missing.
• Reject a wrong field value during Avro schema validation.
• Set error properties to message context.