Skip to content

Releases: linkedin/li-apache-kafka-clients

Modify the delegate client factory for LiKafkaInstrumented clients to take separate properties for base and override configs

28 Aug 18:07
13a4e8c
Compare
Choose a tag to compare

Clients with record header support for timestamp and large message

27 Aug 19:30
4bddf07
Compare
Choose a tag to compare
Add kafka native record headers (#135)

This commit introduces two new kafka native headers
  1. "_t" -- which represents the timestamp at which the message was created by the producer.
  2. "_lm" -- which represents that this message is part of large message.

Add the bounded flush implementation to LiKafkaInstrumentedProducer

21 Aug 22:25
ba70122
Compare
Choose a tag to compare
1.0.9

Add the bounded flush implementation to LiKafkaInstrumentedProducer (…

Bump up Mario version to 0.0.9

05 Aug 20:12
049267a
Compare
Choose a tag to compare
Pre-release
  1. Bump up mario version to 0.0.9 to avoid leaking log4j2 bindings to downstream dependencies
    2.Support config push at boot up time for federated client.

Expose KafkaConsumer API to LiKafkaConsumerImpl

13 Jul 05:40
32eb6db
Compare
Choose a tag to compare

KafkaConsumer has poll(long) and poll(Duration), currently LiKafkaConsumerImpl uses poll(Duration) only, we would like to expose both methods instead.

Add missing methods to kafka-test-harness

24 Jun 18:08
7329ab9
Compare
Choose a tag to compare

Add missing methods from scala based kafka-test-harness

killBroker(int)
killRandomBroker()
restartDeadBrokers()

1.0.4 - Fix in poll() behavior to avoid message loss during consumption

11 Mar 23:26
64c130b
Compare
Choose a tag to compare

Symptom
Current poll() behavior will catch and skip offset on message processing exception and throw the suppressed exception in next poll(). If poll() is not called again and offset is skipped then the user never gets a chance to handle the exception.
All Kafka exceptions are treated as RuntimeException and the message loss can happen if some internal client thread is interrupted which is not a processing exception but an interrupt exception but since its a Kafka exception it is treated as RuntimeException. This caused the offset to move forward without user seing the actual InterruptException and during shutdown if the user commits they will never see the offset that was interrupted.

1.0.3 - Make topic name accessible in the MessageSplitterImpl (#102)

02 Jan 23:47
54c5009
Compare
Choose a tag to compare

A simple bugfix that will make topicName accessible to the SegmentSerializer.

1.0.2 - Pull in Kafka 2.0 clients (#100) (#101)

10 Dec 22:02
756b70f
Compare
Choose a tag to compare

The following changes have been made in addition to bumping up the Kafka version to pull in:

  • LiKafkaConsumerImpl implements new methods in the KafkaConsumer API, including ones that introduce timeouts for existing operations like position, committed, etc.
  • org.apache.kafka.common.protocol.Security is under the package, org.apache.kafka.common.security.auth, in 2.0
  • Redundant API declarations in LiKafkaProducer and LiKafkaConsumer have been removed.

0.0.17 - Porting fixes from internal branch (PR #99)

06 Dec 01:07
c0712ce
Compare
Choose a tag to compare

0.0.17 - Porting fixes from internal branch ( For more details, see PR #99 )