You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2019/10/15 23:03:00 UTC
[jira] [Resolved] (KAFKA-8945) Incorrect null check in the
constructor for ConnectorHealth and AbstractState
[ https://issues.apache.org/jira/browse/KAFKA-8945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Hauch resolved KAFKA-8945.
----------------------------------
Resolution: Fixed
> 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.4.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)