[
https://issues.apache.org/jira/browse/KAFKA-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701151#comment-17701151
]
Chris Egerton commented on KAFKA-14809:
---------------------------------------
This is arguably the root cause of KAFKA-13669, since it's likely that users
would not have been so alarmed by these log messages if they were being emitted
correctly.
It's probably not worth it to revert the downgrade from {{INFO}} to {{DEBUG}}
level at this point, but it's at least worth noting the connection between
these two issues.
> Connect incorrectly logs that no records were produced by source tasks
> ----------------------------------------------------------------------
>
> Key: KAFKA-14809
> URL: https://issues.apache.org/jira/browse/KAFKA-14809
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Hector Geraldino
> Assignee: Hector Geraldino
> Priority: Minor
>
> There's an *{{if}}* condition when [committing
> offsets|https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/WorkerSourceTask.java#L219]
> that is referencing the wrong variable, so the statement always evaluates to
> {*}true{*}.
> This causes log statements like the following to be spuriously emitted:
> {quote}[2023-03-14 16:18:04,675] DEBUG WorkerSourceTask\{id=job-0} Either no
> records were produced by the task since the last offset commit, or every
> record has been filtered out by a transformation or dropped due to
> transformation or conversion errors.
> (org.apache.kafka.connect.runtime.WorkerSourceTask:220)
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
