Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-8947

Connect framework incorrectly instantiates TaskStates for REST extensions

    XMLWordPrintableJSON

    Details

    • 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: KafkaConnect
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ChrisEgerton Chris Egerton
                Reporter:
                ChrisEgerton Chris Egerton
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: