Repository navigation
Bump Confluent.Kafka from 2.14.0 to 2.16.0 - #55
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Confluent.Kafka dependency-version: 2.16.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Confluent.Kafka from 2.14.0 to 2.16.0.
Release notes
Sourced from Confluent.Kafka's releases.
2.16.0
New experimental features
producer or consumer as a builder, which the client invokes during its own
construction and then owns, disposing it (and any Schema Registry client it
created) when the client itself is disposed. See the AvroGeneric example (#2661)
each configurable with a Schema Registry client you own or the
configuration to build one from. See the AvroGeneric,
JsonSerialization and Protobuf examples (#2661)
cluster they're connected to (#2661)
deserializers automatically, and resolved lazily on first use, so subject
name strategies based on the cluster no longer need it configured by hand.
See the AvroGenericAssociation example (#2661)
Set*SerializerBuilderandSet*DeserializerBuilderon the producer and consumer builders, the SchemaRegistry serde builders),
IClusterIdAware,ISerdeDisposable,SerdeExtensionsand the
ClusterIdclient extension are experimental: they are subject tochange or removal in a future release (#2661)
Enhancements
Fixes
platforms, which made encrypted fields unreadable across architectures
Timestamp.Typebeing read asNotAvailableon big-endian platforms(e.g. s390x): librdkafka's
rd_kafka_timestamp_type_tout-parameter (a 32-bit enum)was marshalled as a pointer-sized
IntPtr, so the value landed in the high word andwas truncated to
0on big-endian2.15.1
Enhancements
Fixes
Confluent.Kafkatests (#2656)2.15.0
Upgrade considerations
Ensure you're not calling
StoreOffsetwith an EOF message.As when calling
Commitwith an EOF message, it will throw anInvalidOperationException.Previously this could cause skipping an offset (<2.1.0) or message reprocessing (>=2.1.0).
New features
Confluent.Kafka.OAuthBearer.Awsprovides AWS IAM-basedOAUTHBEARER authentication via AWS STS
GetWebIdentityToken. Activate bysetting
SaslOauthbearerMethod = SaslOauthbearerMethod.Oidc,SaslOauthbearerMetadataAuthenticationType.AwsIam, and supplyingregionandaudienceinSaslOauthbearerConfig. See the package's READMEfor details.
Enhancements
net8.0andnet10.0alongsidenetstandard2.0andnet462. Builds on the approach proposed in #2545 by @ffernandolima, adapted for the centralizedDirectory.Build.propsstructure on current master.Fixes
InvalidOperationExceptionwhen callingStoreOffsetwith an EOF consume result, to matchCommitbehavior (#2621)2.14.2
Enhancements
Fixes
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)