You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2020/01/26 11:46:00 UTC

[jira] [Updated] (KAFKA-9476) Worker throws error "Scanner SubTypeScanner was not configured" when loading invalid jar

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

Chia-Ping Tsai updated KAFKA-9476:
----------------------------------
    Summary: Worker throws error "Scanner SubTypeScanner was not configured" when loading invalid jar  (was: the error "Scanner SubTypeScanner was not configured" caused by invalid jar when starting worker)

> Worker throws error "Scanner SubTypeScanner was not configured" when loading invalid jar
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9476
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9476
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>         Attachments: KAFKA-9476.ut.patch
>
>
> org.reflections 0.9.12 (this [commit|https://github.com/apache/kafka/commit/a024e679c7207aee2242d72aef53dc441c60ca27] updates org.reflections from 0.9.11 to 0.9.12) has a [issue|https://github.com/ronmamo/reflections/issues/273] which throws an error when getting sub classes from invalid plugin (jar file). By contrast, org.reflections 0.9.11 does not. It is a breaking change, and Kafka Worker is impacted. The unit test in attached patch works with org.reflections 0.9.11 but it fails with org.reflections 0.9.12.
> I noticed this issue when running IT of my project with latest Kafka. It is not a critical breaking but it would be better to keep the behavior compatibility. Hence, it seems to me that we can revert the update of org.reflections and then wait for the [issue|https://github.com/ronmamo/reflections/issues/273].
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)