[
https://issues.apache.org/jira/browse/KAFKA-8945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952958#comment-16952958
]
Randall Hauch commented on KAFKA-8945:
--------------------------------------
Merged the backport PR (https://github.com/apache/kafka/pull/7524) to the `2.2`
branch and backported to `2.1` and `2.0`. No need to backport farther back,
since this was a fix for KIP-285 that first appeared in AK 2.0.0.
> Incorrect null check in the constructor for ConnectorHealth and AbstractState
> -----------------------------------------------------------------------------
>
> Key: KAFKA-8945
> URL: https://issues.apache.org/jira/browse/KAFKA-8945
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.3.0
> Reporter: Sanjana Kaundinya
> Assignee: Chris Egerton
> Priority: Major
> Labels: kafka-connect, rest_api
> Fix For: 2.0.2, 2.1.2, 2.2.2, 2.4.0, 2.5.0, 2.3.2
>
>
> This bug is in relation to KIP-285:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-285%3A+Connect+Rest+Extension+Plugin]
> In the constructors of ConnectorHealth.java and AbstractState.java, the check
> that is done for the null parameters is done incorrectly. The current code
> only allows for the class to be instantiated if the parameters passed in are
> null. However the expected behavior has to be the opposite of this: we only
> want this class to be instantiated if the parameters passed in are not null.
> While the fix for this is pretty trivial, it would be good to add in some
> testing that tests the appropriate classes related to the rest extension.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
