Broken shaded internal in kafka sender
See original GitHub issueBundled version of LazyCloseable in kafka-sender 1.0.2 is broken :
...
public void close() throws IOException {
T maybeNull = this.maybeNull();
if (maybeNull != null) {
Util.checkArgument(maybeNull instanceof Closeable, "Override close() to close " + maybeNull, new Object[0]);
((Closeable)maybeNull).close();
}
}
...
In the close method, the Util class is not imported neither shaded in the jar. This leads to a ClassNotFoundException when calling this method.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
org.apache.kafka.common.KafkaException: Failed to construct ...
It has nothing to do with your configuration; it's a class loader problem. Use -verbose JVM arg to see which jars classes are...
Read more >Documentation - Apache Kafka
The internal Kafka Streams producer retries default value was changed from 0 to 10. The internal Kafka Streams consumer max.poll.interval.ms default value ...
Read more >MirrorMaker2 throwing error - NOT_ENOUGH_REPLICAS
I'm running Kafka version 3.0.0 on AKS clusters. The Kafka Cluster definition that I'm using for both the clusters is -.
Read more >Top 5 Things Every Apache Kafka Developer Should Know
However, records aren't stored in one big file but are broken up into segments by partition where the offset order is continuous across...
Read more >Sender · The Internals of Apache Kafka
Sender is created when KafkaProducer is created and immediately started under the name kafka-producer-network-thread | [clientId] (as a daemon thread).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yeah it was an oversight and this problem could bite other libraries, too… Thanks for the shade fix, though!
thanks will fix