[ https://issues.apache.org/jira/browse/FLINK-31018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krzysztof Chmielewski closed FLINK-31018. ----------------------------------------- Resolution: Not A Bug > SQL Client -j option does not load user jars to classpath. > ---------------------------------------------------------- > > Key: FLINK-31018 > URL: https://issues.apache.org/jira/browse/FLINK-31018 > Project: Flink > Issue Type: Bug > Components: Table SQL / Client > Affects Versions: 1.17.0, 1.16.1 > Reporter: Krzysztof Chmielewski > Priority: Minor > Attachments: image-2023-02-10-15-53-39-330.png, > image-2023-02-10-15-54-32-537.png, image-2023-02-10-16-05-12-407.png > > > SQL Client '-j' option does not load custom jars to classpath as it was for > example in Flink 1.15 > As a result Flink 1.16 SQL Client is not able to discover classes through > Flink's Factory discovery mechanism throwing an error like: > {code:java} > [ERROR] Could not execute SQL statement. Reason: > org.apache.flink.table.api.ValidationException: Could not find any factories > that implement 'com.getindata.connectors.http.LookupQueryCreatorFactory' in > the classpath. > {code} > The same Jar and sample job are working fine with Flink 1.15. > Flink 1.15.2 > ./bin/sql-client.sh -j flink-http-connector-0.9.0.jar > !image-2023-02-10-15-53-39-330.png! > Flink 1.16.1 > ./bin/sql-client.sh -j flink-http-connector-0.9.0.jar > !image-2023-02-10-15-54-32-537.png! > ADD JAR command does not solve " Could not find any factories" issue although > jar seems to be added: > !image-2023-02-10-16-05-12-407.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)