Releases: confluentinc/confluent-kafka-dotnet
v2.6.1
v2.6.1 is a maintenance release with the following features, fixes and enhancements:
Enhancements
- References librdkafka.redist 2.6.1. Refer to the librdkafka v2.6.1 release notes for more information.
Fixes
- Fix to continue supporting .NET Framework 4.6.2+ in core client library (#2342).
- Fix JSON Schema handling to not require use of
$id
(#2339). - Update Caching.Memory to 8.0.1 to address CVE (#23440.
- Added Qualified and Custom reference name strategy approaches for protobuf references (#2345).
- Fix validate of SSL CA certs in Schema Registry client (#2346).
- Skip SSL certs validation when configured in Schema Registry client (#2347).
- Allow proxy to be specified in Schema Registry client (#2348).
v2.6.0
v2.6.0 is a feature release with the following features, fixes and enhancements:
Enhancements
- KIP-848 EA: Admin API for listing consumer groups now has an optional filter to return only groups of given types (#2323).
- KIP-460 Admin Leader Election RPC (#2320)
- .NET 8 support with NJsonSchema 11 (#2314)
confluent-kafka-dotnet is based on librdkafka v2.6.0, see the librdkafka release notes for a complete list of changes, enhancements, fixes and upgrade considerations.
v2.5.3
v2.5.3 is a maintenance release with the following fixes and enhancements:
Fixes
- Properly handle messages with well-known types in Protobuf serializer
- Use AES128_GCM in the Local KMS client, for consistency with Java/go
- Include deleted schemas when getting schemas by subject and version
- Handle signed ints when transforming Protobuf payloads
- Allow null SchemaRegistryClient in AsyncSerde constructor
confluent-kafka-dotnet is based on librdkafka v2.5.3, see the librdkafka release notes for a complete list of changes, enhancements, fixes and upgrade considerations.
v2.5.2
Warning
Versions 2.5.0, 2.5.1 and 2.5.2 have a regression in which an assert is triggered during PushTelemetry call. This happens when no metric is matched on the client side among those requested by broker subscription.
You won't face any problem if:
- Broker doesn't support KIP-714.
- KIP-714 feature is disabled on the broker side.
- KIP-714 feature is disabled on the client side. This is enabled by default. Set configuration
enable.metrics.push
tofalse
. - If KIP-714 is enabled on the broker side and there is no subscription configured there.
- If KIP-714 is enabled on the broker side with subscriptions that match the KIP-714 metrics defined on the client.
Having said this, we strongly recommend using v2.5.3
and above to not face this regression at all.
This is a maintenance release.
Fixes
- Fix CSFLE (client-side field-level encryption) to use the Google Tink format for DEKs for interoperability with clients in other languages (Java, go, etc.).
- Improve error when specifying an invalid KMS type for CSFLE
- Enhance CSFLE examples with KMS configuration settings
v2.5.1
This is a maintenance release.
Fixes
- Fix CSFLE (client-side field-level encryption) when using Azure Key Vault by specifying RsaOaep256 (instead of RsaOaep) for interoperability with clients in other languages (Java, go, etc.).
- Fix AvroSerializer configuration to allow using schema normalization.
- Upgrade Azure Identity library to 1.11.4 to address a vulnerability in previous versions.
v2.5.0
This is a feature release
Enhancements
- References librdkafka.redist 2.5.0. Refer to the librdkafka v2.5.0 release notes for more information.
- Add support for metadata and ruleSet in the schema registry client, which together support data
contracts. - Add support for CSFLE (client-side field-level encryption) for AWS, Azure, GCP, and HashiCorp
Vault. See the encryption examples in the examples directory. - Add support for CEL, CEL_FIELD, and JSONata rules.
Fixes
- Switch license expression and other repo information. (#2192, @thompson-tomo)
v2.4.0
This is a feature release.
Enhancements
- References librdkafka.redist 2.4.0. Refer to the librdkafka v2.4.0 release notes for more information.
- KIP-848 EA: Added KIP-848 based new consumer group rebalance protocol.
Integration tests running with the new consumer group protocol. The feature is an Early Access: not production ready. Please refer
detailed doc for more information. (#2212).
2.3.0
This is a feature release.
Enhancements
- References librdkafka.redist 2.3.0. Refer to the librdkafka v2.3.0 release notes for more information.
- KIP-430:
Return authorized operations in describe responses (#2021, @jainruchir). - KIP-396: Added support for ListOffsets Admin API (#2086).
- Add
Rack
to theNode
type, so AdminAPI calls can expose racks for brokers (currently, all Describe
Responses) (#2021, @jainruchir). - Added support for external JSON schemas in
JsonSerializer
andJsonDeserializer
(#2042). - Added compatibility methods to CachedSchemaRegistryClient (ISBronny, #2097).
- Add support for AdminAPI
DescribeCluster()
andDescribeTopics()
(#2021, @jainruchir).
2.2.0
This is a feature release.
Enhancements
- References librdkafka.redist 2.2.0. Refer to the librdkafka v2.2.0 release notes for more information.
- KIP-339
IncrementalAlterConfigs API (#2005). - KIP-554:
User SASL/SCRAM credentials alteration and description (#2070).
Fixes
- Fix backwards compatability of TopicPartitionOffset constructor. (drinehimer, #2066)
- Fix IConsumer breaking change. (ttd2089, #2071)
2.1.1
This is a maintenance release.
Enhancements
- References librdkafka.redist 2.1.1. Refer to the librdkafka v2.1.1 release notes for more information.
- Less heap allocations when calling Produce (bjornbouetsmith, #2020)