Help Center>
Data Lake Insight>
FAQs>
Flink Jobs>
Flink Jar Jobs>
Why Does the Submission Fail Due to Flink JAR File Conflict?
Updated on 2023-05-19 GMT+08:00
Why Does the Submission Fail Due to Flink JAR File Conflict?
Symptom
The dependency of your Flink job conflicts with a built-in dependency of the DLI Flink platform. As a result, the job submission fails.
Solution
Delete your JAR file that is the same as an existing one of the DLI Flink platform.
For details about DLI built-in dependencies, see Built-in Dependencies.
Parent topic: Flink Jar Jobs
Flink Jar Jobs FAQs
- How Do I Configure Checkpoints for Flink Jar Jobs and Save the Checkpoints to OBS?
- Does a Flink JAR Job Support Configuration File Upload? How Do I Upload a Configuration File?
- Why Does the Submission Fail Due to Flink JAR File Conflict?
- Why Does a Flink Jar Job Fail to Access GaussDB(DWS) and a Message Is Displayed Indicating Too Many Client Connections?
- Why Is Error Message "Authentication failed" Displayed During Flink Jar Job Running?
- Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?
- Why Does the Flink Submission Fail Due to Hadoop JAR File Conflict?
- How Do I Connect a Flink jar Job to SASL_SSL?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more
