- Updated kafka client to version 2.3.0
- Added support for
sasl_jaas_config
setting to allow JAAS config per plugin, rather than per JVM #223
- Fixed issue with unnecessary sleep after retries exhausted #216
- Removed obsolete
block_on_buffer_full
,ssl
andtimeout_ms
options
- Added support for kafka property
ssl.endpoint.identification.algorithm
#213
- Changed Kafka client to version 2.1.0
- Changed Kafka client to version 2.0.1 #209
- Upgrade Kafka client to version 2.0.0
- Fixed handling of two settings that weren't wired to the kafka client #198
- Changed Kafka send errors to log as warn #179
- Internal: Update build to gradle
- Upgrade Kafka client to version 1.1.0
- Fix broken 7.0.9 release
- Docs: Set the default_codec doc attribute.
- Improve error logging when a producer cannot be created.
- documentation updates
- bump kafka dependency to 1.0.0
- Update gemspec summary
- Bugfix: Fixed a bug that broke using
org.apache.kafka.common.serialization.ByteArraySerializer
as thevalue_serializer
- Bugfix: Sends are now retried until successful. Previously, failed transmissions to Kafka could have been lost by the KafkaProducer library. Now we verify transmission explicitly. This changes the default 'retry' from 0 to retry-forever. It was a bug that we defaulted to a retry count of 0. #151
- Docs: Fix misleading info about the default codec
- Fix some documentation issues
- Breaking: mark deprecated
block_on_buffer_full
,ssl
andtimeout_ms
options as obsolete
- bump kafka dependency to 0.11.0.0
- bump kafka dependency to 0.10.2.1
- bring back log4j1.x compatibility
- Fix a NPE when SASL_SSL+PLAIN (no Kerberos) was specified.
- Fix a bug where consumer was not correctly setup when
SASL_SSL
option was specified.
- Docs: Update Kafka compatibility matrix
- bump kafka dependency to 0.10.1.1
- Docs: Clarify compatibility matrix and remove it from the changelog to avoid duplication.
- Add Kerberos authentication feature.
- BREAKING: update to 0.10.1.0 client protocol. not backwards compatible with 5.0 (protocol versions <= 10.0.0.1)
- Fix logging
- Update to 0.10.0.1
- Internal: Gem cleanup
- Declare plugin as threadsafe
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Kafka 0.10 broker producer
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- GA release of Kafka Output to support 0.9 broker
- Fix Log4j warnings by setting up the logger (#62)
- Use jar dependencies
- Fixed snappy compression issue
- Internal: Update gemspec dependency
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- [Internal] Pin jruby-kafka to v1.6 to match input
- New dependency requirements for logstash-core for the 5.0 release
- Note: breaking changes in this version, and not backward compatible with Kafka 0.8 broker. Please read carefully before installing
- Breaking: Changed default codec from json to plain. Json codec is really slow when used with inputs because inputs by default are single threaded. This makes it a bad first user experience. Plain codec is a much better default.
- Moved internal APIs to use Kafka's Java API directly instead of jruby-kafka. This makes it consistent with logstash-input-kafka
- Breaking: Change in configuration options
- Added SSL options so you can connect securely to a 0.9 Kafka broker
- [Internal] Pin jruby-kafka to v1.5
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0
- Change to 0.8.2 version of Kafka producer. This will unfortunately break existing configuration, but has a lot of enhancements and fixes.