This topic describes the causes and solutions for error code ODPS-0110061: Failed to run ddltask.
Schema evolution is not enabled in the project
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
Cause
Schema evolution is disabled in the MaxCompute project. Without it, the following DDL operations fail:
-
Adding subcolumns of the STRUCT type
-
Deleting columns
-
Changing the column sequence
-
Changing the data types of columns
Solution
Run the following command to enable schema evolution at the project level:
setproject odps.schema.evolution.enable=true;
The configuration takes effect 10 minutes after you run the command.
For more information about schema evolution, see Partition and column operations.
Concurrent metadata updates cause a transaction abort
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
Cause
Multiple users modified metadata at the same time, causing a metadata conflict. As a result, the transaction was aborted.
Solution
Serialize your DDL operations. Space out metadata updates by at least 1 minute to avoid transaction conflicts.
For more causes and troubleshooting steps for the "Modify DDL meta encounter exception" error, see FAQ about DML operations.