Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump confluent-kafka from 1.7.0 to 2.5.3 in /docker/confluent-kafka #4836

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 3, 2024

Bumps confluent-kafka from 1.7.0 to 2.5.3.

Release notes

Sourced from confluent-kafka's releases.

v2.5.3

confluent-kafka-python v2.5.3

v2.5.3 is a maintenance release with the following fixes and enhancements:

Fixes

  • Fix an assert being triggered during push telemetry call when no metrics matched on the client side.
  • Minor enhancement to JSONDeserializer to retrieve schema from Schema Registry if not provided

confluent-kafka-python 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.0

[!WARNING] This version has introduced 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 to false.
  • 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.

confluent-kafka-python v2.5.0

v2.5.0 is a feature release with the following features, fixes and enhancements:

  • KIP-107 Added delete_records API. (#1710)
  • Added an example to show the usage of the custom logger with AdminClient. (#1758)
  • Improve caching on Schema Registry client. (#1744)
  • Removed usage of strcpy to enhance security of the client. (#1745)
  • Removed support for centos6 and centos7. (#1776)
  • Fixed invalid write in OAUTHBEARER/OIDC extensions copy. (#1745)
  • Fixed documentation for default value of operation_timeout and request_timeout in various Admin apis. (#1710)
  • Fixed an issue related to import error of TopicCollection and TopicPartitionInfo classes when importing through other module like mypy. (#1764)
  • Fixed a segfault when commit or store_offsets consumer method is called incorrectly with errored Message object. (#1754)
  • Fixed logger not working when provided as an argument to AdminClient instead of a configuration property. (#1758)
  • Fixed some memory leaks related to PyDict_SetItem. (#1710)

confluent-kafka-python is based on librdkafka v2.5.0, see the librdkafka release notes for a complete list of changes, enhancements, fixes and upgrade considerations.

v2.4.0

confluent-kafka-python v2.4.0

... (truncated)

Changelog

Sourced from confluent-kafka's changelog.

v2.5.3

v2.5.3 is a maintenance release with the following fixes and enhancements:

Fixes

  • Fix an assert being triggered during push telemetry call when no metrics matched on the client side.
  • Minor enhancement to JSONDeserializer to retrieve schema from Schema Registry if not provided

confluent-kafka-python 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.0

[!WARNING] This version has introduced 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 to false.
  • 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.

v2.5.0 is a feature release with the following features, fixes and enhancements:

  • KIP-107 Added delete_records API. (#1710)
  • Added an example to show the usage of the custom logger with AdminClient. (#1758)
  • Improve caching on Schema Registry client. (#1744)
  • Removed usage of strcpy to enhance security of the client. (#1745)
  • Removed support for centos6 and centos7. (#1776)
  • Fixed invalid write in OAUTHBEARER/OIDC extensions copy. (#1745)
  • Fixed documentation for default value of operation_timeout and request_timeout in various Admin apis. (#1710)
  • Fixed an issue related to import error of TopicCollection and TopicPartitionInfo classes when importing through other module like mypy. (#1764)
  • Fixed a segfault when commit or store_offsets consumer method is called incorrectly with errored Message object. (#1754)
  • Fixed logger not working when provided as an argument to AdminClient instead of a configuration property. (#1758)
  • Fixed some memory leaks related to PyDict_SetItem. (#1710)

confluent-kafka-python is based on librdkafka v2.5.0, see the librdkafka release notes for a complete list of changes, enhancements, fixes and upgrade considerations.

v2.4.0

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [confluent-kafka](https://github.com/confluentinc/confluent-kafka-python) from 1.7.0 to 2.5.3.
- [Release notes](https://github.com/confluentinc/confluent-kafka-python/releases)
- [Changelog](https://github.com/confluentinc/confluent-kafka-python/blob/master/CHANGELOG.md)
- [Commits](confluentinc/confluent-kafka-python@v1.7.0...v2.5.3)

---
updated-dependencies:
- dependency-name: confluent-kafka
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Copy link
Author

dependabot bot commented on behalf of github Oct 11, 2024

Superseded by #5016.

@dependabot dependabot bot closed this Oct 11, 2024
@dependabot dependabot bot deleted the dependabot/pip/docker/confluent-kafka/confluent-kafka-2.5.3 branch October 11, 2024 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants