This topic describes the common configuration parameters in AnalyticDB for MySQL.

ConfigurationParameterDescriptionExampleReferences
Switchover windowREPLICATION_SWITCH_TIME_RANGEThe window during which the existing cluster is switched over to a new cluster. During a switchover to a new cluster, the existing cluster becomes read-only for a period of 5 to 10 minutes. After you are connected to the existing cluster, you can set the REPLICATION_SWITCH_TIME_RANGE parameter to specify the switchover window.
Note If the switchover window is not specified, the existing cluster is switched over to a new cluster after the incremental data of the existing cluster is synchronized in real time to the new cluster.
SET ADB_CONFIG REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;Change cluster configurations (Data Warehouse Edition)
Maximum number of values specified by the IN operatorMAX_IN_ITEMS_COUNTThe maximum number of values that can be specified by the IN operator. Default value: 2000. SET ADB_CONFIG MAX_IN_ITEMS_COUNT=3000;Development FAQ
Query timeout periodQUERY_TIMEOUTThe timeout period of all queries in a cluster. Unit: milliseconds. SET ADB_CONFIG QUERY_TIMEOUT=1000;
The timeout period of a single query. Unit: milliseconds. /*+ QUERY_TIMEOUT=1000 */select count(*) from t;
Timeout period of INSERT, UPDATE, and DELETE statementsINSERT_SELECT_TIMEOUTThe maximum execution duration of the INSERT, UPDATE, and DELETE statements in a cluster. Default value: 24 × 3600000. Unit: milliseconds. SET ADB_CONFIG INSERT_SELECT_TIMEOUT=3600000;Limits
The maximum execution duration of the INSERT, UPDATE, and DELETE statements in a query. Default value: 24 × 3600000. Unit: milliseconds. /*+ INSERT_SELECT_TIMEOUT=3600000 */update customer set customer_name ='adb' where customer_id ='2369';
Filter conditions without pushdown
  • Engine version 3.1.4 or later: FILTER_NOT_PUSHDOWN_COLUMNS
  • Engine version earlier than 3.1.4: NO_INDEX_COLUMNS
Disables filter condition pushdown for specific columns in a cluster.
  • Engine version 3.1.4 or later: set adb_config filter_not_pushdown_columns=[Schema1.tableName1:colName1|colName2;Schema2.tableName2:colName1|colName2]
  • Engine version earlier than 3.1.4: set adb_config no_index_columns=[tableName1.colName1;colName2,tableName2.colName1]
Filter conditions without pushdown
Disables filter condition pushdown for specific columns in a query.
  • Engine version 3.1.4 or later: /*+ filter_not_pushdown_columns=[Schema1.table1:colName1|colName2;Schema2.table2:colName1|colName2] */
  • Engine version earlier than 3.1.4: /*+ no_index_columns=[tableName1.colName1;colName2,tableName2.colName1] */
Query execution modeQUERY_TYPEThe query execution mode of a cluster. Valid values:
  • interactive
  • batch
Note Query execution modes are not supported for Data Warehouse Edition (V3.0) reserved clusters and Data Lakehouse Edition (V3.0) clusters.
SET ADB_CONFIG QUERY_TYPE=interactive;Query execution modes
Query queueXIHE_ENV_QUERY_MAX_CONCURRENT_QUERIESThe maximum number of general queries that can be executed on a single frontend node. Valid values: 1 to 20. Default value: 20. SET ADB_CONFIG XIHE_ENV_QUERY_MAX_CONCURRENT_QUERIES=20;Query throttling configurations
XIHE_ENV_QUERY_MAX_QUEUED_QUERIESThe maximum number of general queries that can be queued on a single frontend node. Valid values: 1 to 200. Default value: 200. SET ADB_CONFIG XIHE_ENV_QUERY_MAX_QUEUED_QUERIES=20;
XIHE_ENV_QUERY_ETL_MAX_CONCURRENT_SIZEThe maximum number of extract-transform-load (ETL) queries that can be executed on a single frontend node. Valid values: 1 to 20. SET ADB_CONFIG XIHE_ENV_QUERY_ETL_MAX_CONCURRENT_SIZE=20;
XIHE_ENV_QUERY_ETL_MAX_QUEUED_SIZEThe maximum number of ETL queries that can be queued on a single frontend node. Valid values: 1 to 100. SET ADB_CONFIG XIHE_ENV_QUERY_ETL_MAX_QUEUED_SIZE=100;
COORDINATOR_QUERY_QUEUEThe queue used by a query. Valid values:
  • low_priority
  • etl
/*+COORDINATOR_QUERY_QUEUE=low_priority*/ select * from tableName limit 100;
Execution priorityDIRECT_LOW_PRIORITY_CPU_QUEUEThe execution priority of a query. /*+DIRECT_LOW_PRIORITY_CPU_QUEUE=true*/ select * from tableName limit 100;
Data import by using MaxCompute external tablesSQL_OUTPUT_BATCH_SIZEThe amount of batch imported data. set adb_config SQL_OUTPUT_BATCH_SIZE = 6000;FAQ on MaxCompute external tables
ENABLE_ODPS_MULTI_PARTITION_PART_MATCHSpecifies whether to obtain the number of entries in each MaxCompute partition in advance. set adb_config ENABLE_ODPS_MULTI_PARTITION_PART_MATCH=false;
Automatic scheduling for BUILD tasksRC_CSTORE_BUILD_SCHEDULE_PERIODThe time range within which you want to schedule BUILD tasks. This parameter is used for scheduling tasks, not for executing tasks. The values of start_time and end_time must be integers. Valid values: 0 to 24. SET ADB_CONFIG RC_CSTORE_BUILD_SCHEDULE_PERIOD=`<start_time>,<end_time>`;Configure automatic scheduling for BUILD tasks
Scheduling priority of BUILD tasksbuild_task_priorityConfigures a scheduling priority for only one table. The configured priority takes effect only for the current BUILD task.

The task_priority parameter specifies the scheduling priority of BUILD tasks. The value must be an integer. The default value is 0.

/*build_task_priority = <task_priority> */ BUILD TABLE <db_name>.<table_name>;Configure scheduling priorities for BUILD tasks
ADB_CONFIG RC_BUILD_TASK_PRIORITY_LISTConfigures scheduling priorities for one or more tables. The configured priorities are effective until you configure new scheduling priorities of BUILD tasks for the tables.

The task_priority parameter specifies the scheduling priority of BUILD tasks. The value must be an integer. The default value is 0.

SET ADB_CONFIG RC_BUILD_TASK_PRIORITY_LIST = `<db1_name>.<table1_name>.<task_priority>;<db2_name>.<table2_name>.<task_priority>`;