logstash-integration-kafka 11.7.0-java → 11.8.0-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 73e5319cf0e521282ced1615e3cb864ae58fd4195b39a67e42ff995cb22d5004
-  data.tar.gz: 380f7e07b99231ae047fc8545e7be56132f92b7d8179ae97a1f7f95c49a01033
+  metadata.gz: 101a2c1fc70011cadd866f4aeca79850045a51272eac7d704e766a2e08353c52
+  data.tar.gz: e51c20830a9d22d4e049288a3ab1c152db33121a87a73d08d493f681df707fec
 SHA512:
-  metadata.gz: 88d9dcbab467d2dc1af0e79e3b76af0cfdb3e2398644f1d4337414965c67813ee6d6829478c3bce8d082bbde269e34c134867a0831d0c4235cf9855c388597cf
-  data.tar.gz: 840eb2502efc99a1517790f315bb4a181697345eb422d36e64f7cf4d577999415acc43c32174ce905e31d0cd5cc00bd8f1b16962e26c78617db8fef3397280dd
+  metadata.gz: f17d5f0e28dff57741485e1d3aed9bca31cbf4a6b7a1b1950220cda6d2e8b23f0afbb29a9a3fa6797469941c8e116ab0fbff8bc6a6573f6b9b7a91d472a53323
+  data.tar.gz: 293e08920a1560bd5405479ea8313336fed652abd51f64038b2e7628a5978da486e7eb00fa2aa577b0f54b93bff90943051bb76509f597f18e2417a7a2fbb3d9

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 11.8.0
+  - Deprecate partitioner `default` and `uniform_sticky` options [#206](https://github.com/logstash-plugins/logstash-integration-kafka/pull/206)
+      Both options are deprecated in Kafka client 3 and will be removed in the plugin 12.0.0.
+
 ## 11.7.0
   - Add `reconnect_backoff_max_ms` option for configuring kafka client [#204](https://github.com/logstash-plugins/logstash-integration-kafka/pull/204)
 

data/docs/output-kafka.asciidoc

@@ -349,14 +349,15 @@ The max time in milliseconds before a metadata refresh is forced.
 * Value type is <<string,string>>
 * There is no default value for this setting.
 
-The default behavior is to hash the `message_key` of an event to get the partition.
-When no message key is present, the plugin picks a partition in a round-robin fashion.
+By not setting this value, the plugin uses the built-in partitioning strategy provided by the Kafka client. Read more about the "partitioner.class" on the Kafka documentation.
 
-Available options for choosing a partitioning strategy are as follows:
+Available options are as follows:
 
-* `default` use the default partitioner as described above
+* `default` hashes the `message_key` of an event to get the partition. When no message key is present, the plugin picks a partition in a round-robin fashion. Please note that this is a different strategy than the one used when `partitioner` is left unset.
 * `round_robin` distributes writes to all partitions equally, regardless of `message_key`
-* `uniform_sticky` sticks to a partition for the duration of a batch than randomly picks a new one
+* `uniform_sticky` hashes the `message_key` of an event to get the partition. When no message key is present, the plugin sticks to a partition for the duration of a batch than randomly picks a new one.
+
+NOTE: `default` and `uniform_sticky` are deprecated and will be removed in `12.0.0`.
 
 [id="plugins-{type}s-{plugin}-receive_buffer_bytes"]
 ===== `receive_buffer_bytes` 

data/lib/logstash/outputs/kafka.rb

@@ -409,8 +409,10 @@ class LogStash::Outputs::Kafka < LogStash::Outputs::Base
     when 'round_robin'
       'org.apache.kafka.clients.producer.RoundRobinPartitioner'
     when 'uniform_sticky'
+      log_partitioner_warning(partitioner, 'UniformStickyPartitioner')
       'org.apache.kafka.clients.producer.UniformStickyPartitioner'
     when 'default'
+      log_partitioner_warning(partitioner, 'DefaultPartitioner')
       'org.apache.kafka.clients.producer.internals.DefaultPartitioner'
     else
       unless partitioner.index('.')
@@ -420,4 +422,10 @@ class LogStash::Outputs::Kafka < LogStash::Outputs::Base
     end
   end
 
+  def log_partitioner_warning(partitioner, class_name)
+    deprecation_logger.deprecated("Producer `partitioner` is configured with the deprecated option `#{partitioner}`. " \
+                  "#{class_name} is removed in kafka-client 4.0 and the `#{partitioner}` option will be removed in the plugin 12.0.0. "\
+                  'Please update your configuration to use `round_robin` or unset the option to use the build-in partitioning strategy. ')
+  end
+
 end #class LogStash::Outputs::Kafka

data/logstash-integration-kafka.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name            = 'logstash-integration-kafka'
-  s.version         = '11.7.0'
+  s.version         = '11.8.0'
   s.licenses        = ['Apache-2.0']
   s.summary         = "Integration with Kafka - input and output plugins"
   s.description     = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline "+

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: logstash-integration-kafka
 version: !ruby/object:Gem::Version
-  version: 11.7.0
+  version: 11.8.0
 platform: java
 authors:
 - Elastic
 bindir: bin
 cert_chain: []
-date: 2025-10-03 00:00:00.000000000 Z
+date: 2025-10-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logstash-core-plugin-api