[
https://issues.apache.org/jira/browse/KAFKA-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700360#comment-17700360
]
Chris Egerton commented on KAFKA-14809:
---------------------------------------
[~hgeraldino] I wanted a Jira ticket for this so that users could easily find
the cause of the problem if they were confused by the incorrect log messages,
so I've taken a stab at changing the title and description to describe not just
the specific bug in the code, but the user-facing effects that it has. Feel
free to alter anything you'd like; I just want this to be discoverable by users
who may be searching for, e.g., log messages to understand what's going wrong.
> 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)
