- Updated Kafka client version to 2.3.0
- Added support for
sasl_jaas_config
setting to allow JAAS config per plugin, rather than per JVM #313
- Removed obsolete
ssl
option
- Added support for kafka property ssl.endpoint.identification.algorithm #302(#302)
- Changed Kafka client version to 2.1.0
- Changed Kafka client version to 2.0.1 #295
- Upgrade Kafka client to version 2.0.0
- Docs: Correct list formatting for
decorate_events
- Docs: Add kafka default to
partition_assignment_strategy
- Fix race-condition where shutting down a Kafka Input before it has finished starting could cause Logstash to crash
- Internal: Update build to gradle
- Upgrade Kafka client to version 1.1.0
- Fix broken 8.0.5 release
- Docs: Set the default_codec doc attribute.
- Upgrade Kafka client to version 1.0.0
- Update gemspec summary
- Fix some documentation issues
- Fixed an issue that prevented setting a custom
metadata_max_age_ms
value
- Breaking: mark deprecated
ssl
option as obsolete
- Breaking: Nest the decorated fields under
@metadata
field to avoid mapping conflicts with beats. Fixes #198, #180
- Fix an issue that led to random failures in decoding messages when using more than one input thread
- Upgrade Kafka client to version 0.11.0.0
- fix: Added record timestamp in event decoration
- Upgrade Kafka client to version 0.10.2.1
- Fix NPE when SASL_SSL+PLAIN (no Kerberos) is specified.
- fix: Client ID is no longer reused across multiple Kafka consumer instances
- Fix a bug where consumer was not correctly setup when
SASL_SSL
option was specified.
- Make error reporting more clear when connection fails
- Docs: Update Kafka compatibility matrix
- update kafka-clients dependency to 0.10.1.1
- Docs: Clarify compatibility matrix and remove it from the changelog to avoid duplication.
- Expose config
max_poll_interval_ms
to allow consumer to send heartbeats from a background thread - Expose config
fetch_max_bytes
to control client's fetch response size limit
- Add Kerberos authentication support.
- default
poll_timeout_ms
to 100ms
- Breaking: Support for Kafka 0.10.1.0. Only supports brokers 0.10.1.x or later.
- place setup_log4j for logging registration behind version check
- Update to Kafka version 0.10.0.1 for bug fixes
- Internal: gem cleanup
- Release a new version of the gem that includes jars
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Support for Kafka 0.10 which is not backward compatible with 0.9 broker.
- 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
- Support for Kafka 0.9 for LS 5.x
- Fix Log4j warnings by setting up the logger
- Internal: Use jar dependency
- Fixed issue with snappy compression
- Internal: Update gemspec dependency
- internal: Use jar dependencies library instead of manually downloading jars
- Fixes "java.lang.ClassNotFoundException: org.xerial.snappy.SnappyOutputStream" issue (#50)
- Added SSL/TLS connection support to Kafka
- Breaking: Changed default codec to plain instead of SSL. 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.
- Refactor to use new Java based consumer, bypassing jruby-kafka
- Breaking: Change configuration to match Kafka's configuration. This version is not backward compatible
- Update to jruby-kafka 1.6 which includes Kafka 0.8.2.2 enabling LZ4 decompression.
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Fix safe shutdown while plugin waits on Kafka for new events
- Expose auto_commit_interval_ms to control offset commit frequency
- Fix infinite loop when no new messages are found in Kafka
- 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