Help Center>
Cloud Data Migration>
FAQs>
Troubleshooting>
Hudi Destination Case Library>
What Should I Do If the Auto Creation of the Hudi Table Fails Due to a Schema Mismatch?
Updated on 2023-06-21 GMT+08:00
What Should I Do If the Auto Creation of the Hudi Table Fails Due to a Schema Mismatch?
Symptom
When CDM migrates data to Hudi and automatic table creation is enabled for Hudi, the schema mismatch error "org.apache.spark.sql.AnalysisException:Specified schema in create table statement is not equal to the table schema" is reported when the table creation statement is executed.
Possible Cause
A table is deleted from MetaStore, but the file is not cleared. The directory file of the table exists. A foreign table may be created.
Solution
Clear the table directory and run the job again.
Parent topic: Hudi Destination Case Library
Hudi Destination Case Library FAQs
- What Should I Do If the Auto Creation of the Hudi Table Fails Due to a Schema Mismatch?
- What Should I Do If a Hudi Job Stays in Booting Status for a Long Time and then Fails and the "Read timed out" Error Is Contained in the Log?
- What Should I Do If the Number of Read Rows Is the Same as That of Write Rows, Both Numbers No Longer Increase, and the Job Stays in Running State?
- What Should I Do If a Job Stays in Running State but the Number of Written Rows Is 0?
- What Should I Do If Data Fails to Be Written to Hudi Using Spark SQL?
- What Should I Do If a Job Fails Due to Intermittent Disconnection, Timeout, or Connection Termination of the Source Link?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
