[KAFKA-14809] Connect incorrectly logs that no records were produced by source tasks

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.0, 3.0.0, 3.0.1, 3.2.0, 3.1.1, 3.3.0, 3.0.2, 3.1.2, 3.2.1, 3.4.0, 3.2.2, 3.2.3, 3.3.1, 3.3.2
• Fix Version/s: 3.2.4, 3.1.3, 3.0.3, 3.5.0, 3.4.1, 3.3.3
• Component/s: connect
• Assignee: Hector Geraldino
• Reporter: Hector Geraldino
• Created: 14/Mar/23 20:05
• Updated: 16/Mar/23 12:46
• Resolved: 16/Mar/23 12:46

Description

There's an if condition when committing offsets that is referencing the wrong variable, so the statement always evaluates to true.

This causes log statements like the following to be spuriously emitted:

[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)

Issue Links

• causes: KAFKA-13669 Log messages for source tasks with no offsets to commit are noisy and confusing
• links to: GitHub Pull Request #13386