OmniAdvisor Database Tables

OmniAdvisor uses a PostgreSQL database, leveraging the omniadvisor_exam_record, omniadvisor_load, and omniadvisor_tuning_record tables to manage data throughout the Spark task tuning process.

Table 1 describes the name and meaning of each field in the database tables.

**Table 1** Fields in the database tables
Table Name	Field Name	Description
omniadvisor_exam_record	id	Auto-generated primary key
	tuning_record_id	ID of the tuning record associated with the test record
	start_time	Spark task start time
	end_time	Spark task end time
	status	Whether the Spark task is successfully executed
	runtime	Spark task execution duration
	application_id	application_id of the Spark task
	sql_trace	sql_trace data generated during Spark task execution
	stage_trace	stage_trace data generated during Spark task execution
omniadvisor_load	id	Auto-generated primary key
	name	Load name
	exec_attr	Load execution characteristics
	default_config	Default configuration
	best_config	Historical optimal configuration
	test_config	Configuration to be retested
	create_time	Load creation time
	tuning_needed	Whether tuning is required
	hash_value	Hash value calculated based on exec_attr and default_config
	backend_retest_enable	Whether the load supports background retests
omniadvisor_tuning_record	id	Auto-generated primary key
	load_id	Load ID associated with the tuning record
	config	Tuning configuration
	method	Tuning method
	method_extend	Subclasses of the tuning method
	rounds	Number of tuning rounds

In the omniadvisor_exam_record table, the start_time and end_time fields are stored in the UTC time zone. This storage mode may differ from the time zone used by the server.

For example, you can run the SET timezone command of the PostgreSQL database to set the time zone to Asia/Shanghai.

SET timezone TO 'Asia/Shanghai';

Parent topic: References