[ 
https://issues.apache.org/jira/browse/KAFKA-13989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomasz updated KAFKA-13989:
---------------------------
    Description: 
When a connector plugin gets removed from the Kafka Connect, the 
{{/connectors?expand=info}} or {{/connectors?expand=status}} call returns

{ "error_code": 500, "message": "Failed to find any class that implements 
Connector and which name matches ..." }

without any other connector info. My expectation would be to return all valid 
connectors and an error status for the unsupported one.

The {{/connectors}} call on the other hand, returns the defined connector list.

 

  was:
When a connector plugin gets removed from the Kafka Connect, the 
{{/connectors?expand=info}} or {{/connectors?expand=status}} call returns

{{{ "error_code": 500, "message": "Failed to find any class that implements 
Connector and which name matches ..." }}}

without any other connector info. My expectation would be to return all valid 
connectors and an error status for the unsupported one.

The {{/connectors}} call on the other hand, returns the defined connector list.

 


> Get connectors call fails when plugin removed
> ---------------------------------------------
>
>                 Key: KAFKA-13989
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13989
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 3.1.0
>            Reporter: Tomasz
>            Priority: Minor
>
> When a connector plugin gets removed from the Kafka Connect, the 
> {{/connectors?expand=info}} or {{/connectors?expand=status}} call returns
> { "error_code": 500, "message": "Failed to find any class that implements 
> Connector and which name matches ..." }
> without any other connector info. My expectation would be to return all valid 
> connectors and an error status for the unsupported one.
> The {{/connectors}} call on the other hand, returns the defined connector 
> list.
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to