This topic describes the possible causes of the error code ODPS-0110061: Failed to run ddltask and provides solutions.
Error message 1: Schema evolution DDLs is not enabled in current project:xxxx
Sample
FAILED: Catalog Service Failed, ErrorCode: 152, Error Message: ODPS-0110061: Failed to run ddltask-Schema evolution DDLs is not enabled in current project:xxxx
Description
Schema evolution is not allowed in the MaxCompute project. For example, you cannot add subcolumns of the STRUCT type, delete columns, change the column sequence, or change the data types of columns.
Solution
To enable the schema evolution feature, run the setproject odps.schema.evolution.enable=true; command. The configuration takes effect 10 minutes after you run the preceding command. For more information about schema evolution, see Partition and column operations.
Error message 2: ODPS-0110061: Failed to run ddltask - Modify DDL meta encounter exception
Sample
ODPS-0110061: Failed to run ddltask - Modify DDL meta encounter exception : ODPS-0429311:Transaction aborted - MaxC Transaction aborted. Can't update ObjectId(objectType:PARTITION, dbName:mc_gjpt, tableName:xxxx, tableId:xxx, partitionId:xxxx, partitionName:pt=20221125, tenantId:, catalogName:xxx, catalogId:xxx, dbId:, projectName:xxx). BeginTs is less than lastCommitTs.objectId:ObjectId(objectType:PARTITION, dbName:xxx, tableName:xxxx, tableId:xxx, partitionId:xxx, partitionName:pt=20221125, tenantId:, catalogName:xxxx, catalogId:xxx, dbId:, projectName:xxxx), txnId:xxxxx, lastCommitTs:1709410212584448, lastMaxBeginTs:1709410182400000, isolation:NONSTRICT_SNAPSHOT_ISOLATION, op:UPDATE, isConstraintNotAllowInsertIntoReorder:false
Description
Metadata is changed by multiple users at the same time. As a result, a metadata conflict occurs.
Solution
We recommend that you update metadata at a minimum interval of 1 minute.