Ted
I don't see any other INFO log messages so I assume that means it is the
DEBUG case I'm seeing?
I don't have DEBUG enabled at the moment.
Thanks
On Wed, 13 Jun 2018, 00:21 Ted Yu, wrote:
> Before Errors.INVALID_FETCH_SESSION_EPOCH is returned, FetchSession.scala
> would log the reason for
In log4j.properties, can you make the following change (you can keep
whatever follows the first comma in the rootLogger line):
log4j.rootLogger=DEBUG
log4j.logger.org.apache.kafka=DEBUG
FetchSession.scala is in kafka.server package. You can just turn on DEBUG
for this package.
FYI
On Wed, Jun
Hi,
In kafka stream, when we use *to *method for sending values to a topic, is
there a way to mention the message key .
.to(outputTopic, Produced.with(byteArraySerde, itemEnvelopeSerde));
In Produced class , i cant find a way to set the key.
https://kafka.apache.org/10/javadoc/org/apache/kafka/s
Hi Manikumar!
Thanks for responding! Sorry it took me so long to get back!
We did end up turning on debug logs for the console consumer and found that one
broker seemed to be having problems, it would lead to timeouts communicating
with it. After restarting that broker, things sorted themselv
.to() method is called on KStream, like KStream.to(outputTopic, Produced
),
See sample code below-
KStream inputStream = builder.stream("input-topic");
KStream outputStream = inputStream.map(new
KeyValueMapper> {
KeyValue apply(String key, String value) {
return new KeyValue<>
