Confluent Consume

Release date 2026/08/24

Bugfix

• Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

• Fixed the confluent schema registry client caching fetched schemas and subjects under keys that did not account for the registry URL or authentication. Instances configured with different credentials could be served each other’s cached lookups, letting an unauthorized instance bypass schema-registry authentication once any authorized instance had warmed the cache. Cache entries are now scoped to the registry identity, and the configured schema_registry.confluent.ttl is now applied to these cache entries.

• Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

• Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

Release date 2026/07/02

Feature

• Added SASL OAUTHBEARER authentication support.

Release date 2026/08/26

Bugfix

• Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

• Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

Release date 2026/07/29

Bugfix

• Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

Release date 2026/04/07

Feature

• the ssl_verify option to validate the server certificate is now enabled by default.

Release date 2026/08/20

Bugfix

• Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

• Fixed an issue where OAuth2 authentication against Confluent Cloud Schema Registry failed because the client did not send the required target-sr-cluster header.

Release date 2025/12/18

Feature

• added new config option tls_certificate_verify to support verifying server certificates. Added support for the tls_certificate_verify global option. When this option is enabled, the plugin’s tls_certificate_verify setting cannot be disabled.

Bugfix

• Fixed an issue where the plugin would fail to connect using mTLS.

Release date 2026/09/02

Bugfix

• Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

Release date 2026/08/18

Bugfix

• Fixed a crash that occurred when a plugin set schema_registry.confluent.authentication.mode to oauth2 but omitted the oauth2_client record. Previously this returned a 500 from the Admin API during validation, and once saved it also crashed at runtime while fetching the schema registry OAuth2 token. The absent oauth2_client is now handled and falls back to the default authentication method, so a configuration without oauth2_client works end-to-end.

Release date 2026/07/22

Bugfix

• Fixed Kafka keepalive pools leaking connections across different SASL credentials and TLS verification settings.

• Fixed Kafka broker returning failed connections to the keepalive pool, added SSL handshake retry, and improved error propagation.

Release date 2025/11/18

Bugfix

• Fixed an issue where the plugin would fail to connect using mTLS.

Release date 2025/10/01

Feature

• Added websocket mode to the confluent-consume plugin.

Release date 2025/10/23

Bugfix

• Fixed an issue where the plugin would fail to connect using mTLS.

Release date 2026/08/31

Bugfix

• Fixed a permanent failure that started when a broker answered an ApiVersions request with an error code, an empty API key set, or a malformed frame. The client cached that result and every later request failed with ProduceRequest API version not negotiated; broker may be unreachable until the node restarted, even after the broker recovered. The client now refuses an unusable ApiVersions response, keeps the previous negotiation, and retries the negotiation for a topic whose metadata is already cached.

Release date 2025/10/10

Bugfix

• Added enforce_latest_offset_reset flag to fix incorrect latest offset behavior. When false (default), maintains backwards compatibility where latest acts like earliest. When true, latest correctly starts from end of topic. Also fixed offset commit bug when no records are consumed, preventing feedback loop with true latest behavior.

• Fixed an issue where the plugin would fail to connect using mTLS.

Release date 2025/03/27

Known Issues

• An error message appears in the logs about a missing cluster name, even when the name is specified.