Help Center/ Data Lake Insight/ FAQs/ Spark Jobs/ Spark Job O&M/ Why Is the global_temp Database Missing in the Job Log of Spark 3.x?

Updated on 2024-11-15 GMT+08:00

View PDF

Why Is the global_temp Database Missing in the Job Log of Spark 3.x?

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: Spark Job O&M

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot