Hi, Perez.
Flink use SPI to find the jdbc connector in the classloader and when starting,
the dir '${FLINK_ROOT}/lib' will be added
into the classpath. That is why in AWS the exception throws. IMO there are two
ways to solve this question.
1. upload the connector jar to AWS to let the classloader keep this jar. As for
how to upload connector jars, you need to check
the relevant documents of AWS.
2. package the jdbc connector jar into your job jar and submit it again.
--
Best！
Xuyang
At 2024-04-10 17:32:19, "Enrique Alberto Perez Delgado"
<[email protected]> wrote:
Hi all,
I am using AWS Managed Flink 1.18, where I am getting this error when trying to
submit my job:
```
Caused by: org.apache.flink.table.api.ValidationException: Cannot discover a
connector using option: 'connector'='jdbc' at
org.apache.flink.table.factories.FactoryUtil.enrichNoMatchingConnectorError(FactoryUtil.java:798)
at
org.apache.flink.table.factories.FactoryUtil.discoverTableFactory(FactoryUtil.java:772)
at
org.apache.flink.table.factories.FactoryUtil.createDynamicTableSink(FactoryUtil.java:317)
... 32 more Caused by: org.apache.flink.table.api.ValidationException: Could
not find any factory for identifier 'jdbc' that implements
'org.apache.flink.table.factories.DynamicTableFactory' in the classpath.
```
I used to get this error when testing locally until I added the
`flink-connector-jdbc-3.1.2-1.18`.jar to `/opt/flink/lib` in my local docker
image, which I thought would be provided by AWS. apparently, it isn’t. Has
anyone encountered this error before?
I highly appreciate any help you could give me,
Best regards,
Enrique Perez
Data Engineer
HelloFresh SE | Prinzenstraße 89 | 10969 Berlin, Germany
Phone: +4917625622422
| |
HelloFresh SE, Berlin (Sitz der Gesellschaft) | Vorstände: Dominik S. Richter
(Vorsitzender), Thomas W. Griesel, Christian Gärtner, Edward Boyes |
Vorsitzender des Aufsichtsrats: John H. Rittenhouse | Eingetragen beim
Amtsgericht Charlottenburg, HRB 182382 B | USt-Id Nr.: DE 302210417
CONFIDENTIALITY NOTICE: This message (including any attachments) is
confidential and may be privileged. It may be read, copied and used only by the
intended recipient. If you have received it in error please contact the sender
(by return e-mail) immediately and delete this message. Any unauthorized use or
dissemination of this message in whole or in parts is strictly prohibited.
