[jira] [Resolved] (KAFKA-20751) Cached connector plugin version validation failures lose available versions on repeated validation

["Mickael Maison (Jira)" <ji...@apache.org>]

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

Mickael Maison resolved KAFKA-20751.
------------------------------------
    Fix Version/s: 4.4.0
       Resolution: Fixed

> Cached connector plugin version validation failures lose available versions on repeated validation
> --------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-20751
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20751
>             Project: Kafka
>          Issue Type: Bug
>          Components: connect
>            Reporter: majialong
>            Assignee: majialong
>            Priority: Minor
>             Fix For: 4.4.0
>
>
> CachedConnectors, introduced as part of KAFKA-18215, caches connector loading failures during config validation.
>  
> When validating a connector configuration with an unavailable connector.plugin.version, the first validation response correctly reports the available plugin versions in the connector.plugin.version recommended values.
>  
> Repeating the same validation may return an inconsistent result: the cached failure path loses the available versions from the original VersionedPluginLoadingException.
> The repeated validation can then fail with a NullPointerException in AbstractHerder.invalidVersionedConnectorValidation, when it attempts to stream VersionedPluginLoadingException#availableVersions() to populate the connector.plugin.version recommended values, resulting in a 500 response instead of the normal validation response.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)