[KAFKA-8947] Connect framework incorrectly instantiates TaskStates for REST extensions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1, 2.0.2, 2.3.0, 2.1.2, 2.2.1, 2.2.2, 2.4.0, 2.3.1, 2.2.3
• Fix Version/s: 2.0.2, 2.1.2, 2.2.2, 2.4.0, 2.3.2
• Component/s: connect
• Assignee: Chris Egerton
• Reporter: Chris Egerton
• Created: 26/Sep/19 17:29
• Updated: 16/Oct/19 15:56
• Resolved: 16/Oct/19 15:56

Description

The TaskState class's constructor takes in parameters for the task's ID number, state, worker, and (optionally-null) error stack trace, in that order. However, the Connect framework's ConnectClusterStateImpl class instantiates TaskState objects with a different ordering of arguments: ID number, worker, state, trace.

It's possible that this (erroneous) behavior has already been identified and worked around by developers of REST extensions, so it's questionable whether a patch PR here is warranted.

Issue Links

• relates to: KAFKA-8945 Incorrect null check in the constructor for ConnectorHealth and AbstractState