Help Center>
Data Lake Insight>
FAQs>
Problems Related to Spark Jobs>
Job O&M Errors>
Why Can't I Find the global_temp Database in the Spark 3.x Job Log?
Updated on 2023-05-19 GMT+08:00
Why Can't I Find the global_temp Database in the Spark 3.x Job Log?
Symptom
I cannot find the global_temp database in the Spark 3.x job log.
Possible Causes
The global_temp database is the default built-in database of Spark 3.x and is Spark's global temporary view.
When a Spark job is registered with ViewManager, the system checks whether the database exists in Metastore. If it is, the Spark job fails to be executed.
If the Spark 3.x job log contains a record of accessing catalogs to query the database and a message indicating that the non-existence of the database is to ensure that Spark jobs can run properly, you do not need to perform any operations.
Parent topic: Job O&M Errors
Job O&M Errors FAQs
- What Can I Do When Receiving java.lang.AbstractMethodError in the Spark Job?
- Why Are Errors "ResponseCode: 403" and "ResponseStatus: Forbidden" Reported When a Spark Job Accesses OBS Data?
- Why Is Error "verifyBucketExists on XXXX: status [403]" Reported When I Use a Spark Job to Access an OBS Bucket That I Have Access Permission?
- Why Is a Job Running Timeout Reported When a Spark Job Runs a Large Amount of Data?
- Why Does the Job Fail to Be Executed and the Log Shows that the File Directory Is Abnormal When I Use a Spark Job to Access Files in SFTP?
- Why Does the Job Fail to Be Executed Due to Insufficient Database and Table Permissions?
- Why Can't I Find the global_temp Database in the Spark 3.x Job Log?
- Why Does the DataSource Syntax Fail to Create an OBS Table in Avro Format When Spark 2.3.x Is Used?
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
