Error codes
|
HTTP status code |
Error code |
Error message |
Description |
Action |
| 400 | Action.BlueprintInstance.Run.Failed | Failed to run the blueprint instance. | An error occurred while running the workflow. | diagnosis |
| 400 | Action.Unsupported | The operation is not supported. | Unsupported operation. | diagnosis |
| 409 | AlreadyExists | Database, table, partition or function already exists. | An object with the same name already exists, such as a metadatabase, metatable, partition, or function. Do not add duplicate objects. | diagnosis |
| 500 | InternalError | An internal error occurred. | An unknown error occurred. Resolve the issue based on the error message. | diagnosis |
| 400 | InvalidObject | The object is invalid. The issue is due to one of the following. Incomplete partition name/invalid partition column/invalid skew column/storage descriptor cannot be null/invalid table columns/invalid object name/cannot find database or table. | Input parameter validation failed. Check whether the parameter names and quantity are correct based on the error message, and verify that the format and length meet the requirements. Also verify that the objects corresponding to the input parameters, such as metadatabases and metatables, exist. | diagnosis |
| 403 | InvalidOperation | The operation is invalid. Scenario 1: Corresponding Table or Database does not exist. Scenario 2: Unable to access old location. The new location of the table is on a different file system than the old location. Scenario 3: The name of table or partition already exists when you rename. | The operation is invalid. This error typically occurs when the related data cannot be found or a conflict exists during an update or delete operation. For example, the metadatabase or metatable does not exist, a rename conflict exists, or the location is incorrect. Check whether the related configurations are correct based on the error message. | diagnosis |
| 400 | InvalidParams | The specified parameter is invalid. | Input error. Check the input data. | diagnosis |
| 400 | InvalidParams.Empty | You must specify the parameter. | The parameter is empty. | diagnosis |
| 404 | NoSuchObject | Cannot find corresponding object. Scenario 1: Column stats does not exist. Scenario 2: Database does not exist. Scenario 3: Function does not exist. Scenario 4: Partition does not exist. Scenario 5: Table does not exist. | The related object does not exist and the operation cannot be executed. For example, the metadatabase, metatable, metatable partition, or statistics information of the metatable partition does not exist. Confirm that the related IDs are correct, and pay attention to case sensitivity and special characters. | diagnosis |
| 400 | Query.ClusterNotReady | Query cluster is not ready. Please try again later. | The cluster resource for the query is being prepared. Try again later. | diagnosis |
| 400 | Query.PageNumOverLimit | The page number limit is exceeded. Please export to get more data. | The number of pages exceeds the limit. To obtain more data, export the data or query the result table. | diagnosis |
| 400 | Query.ResultExpired | Query result cache expired. Please export results in history query. | The page results have expired. Export the results from the run history to view them. | diagnosis |
| 400 | Query.TempDBNotExist | The temp database does not exist. Please configure OSS path first. | The query result path has not been configured. Configure the path first. | diagnosis |
| 403 | RAM.Permission.NotAllow | You are not authorized to perform the operation. Please use RAM to authorize the operation. | You do not have the required permissions. Use RAM authorization to grant the permissions. | diagnosis |
| 413 | RequestEntityTooLarge | Request Entity Too Large. | The request body is too large. For example, the request contains too many request parameters or the parameter values are too long. | diagnosis |
| 400 | Resource.BlueprintInstance.NotExist | The blueprint instance does not exist. | The data ingestion template instance does not exist. | diagnosis |
| 400 | Resource.Workflow.NotExist | The workflow does not exist. | The workflow instance does not exist. | diagnosis |
| 404 | UnknownDB | Unable to ${action} database. | The corresponding metadatabase cannot be found and the operation cannot be performed. Check whether the parameters such as the name are correct, and pay attention to case sensitivity. | diagnosis |
| 404 | UnknownPartition | Unable to ${action} partition. | The corresponding metatable partition cannot be found and the operation cannot be performed. Check whether the number and names of partitions are correct and whether the partition already exists. | diagnosis |
| 404 | UnknownTable | ${tableName} does not exist. | The corresponding metatable cannot be found. Check whether the parameters such as the name are correct, and pay attention to case sensitivity. | diagnosis |