ScalarDB Error Codes
This page provides a list of error codes in ScalarDB.
Error code classes and descriptions​
| Class | Description |
|---|---|
CORE-1xxxx | Errors for the user error category |
CORE-2xxxx | Errors for the concurrency error category |
CORE-3xxxx | Errors for the internal error category |
CORE-4xxxx | Errors for the unknown transaction status error category |
CORE-1xxxx status codes​
CORE-10000​
Message
Only a single-column index is supported. Operation: %s
CORE-10001​
Message
The column of the specified index key is not indexed. Operation: %s
CORE-10002​
Message
The index key is not properly specified. Operation: %s
CORE-10003 ​
Message
Clustering keys cannot be specified when using an index. Operation: %s
CORE-10004​
Message
Orderings cannot be specified when using an index. Operation: %s
CORE-10005​
Message
The limit cannot be negative. Operation: %s
CORE-10006​
Message
Cross-partition scan is not enabled. Operation: %s
CORE-10007​
Message
Cross-partition scan ordering is not enabled. Operation: %s
CORE-10008​
Message
Cross-partition scan filtering is not enabled. Operation: %s
CORE-10009​
Message
The specified projection is not found. Projection: %s, Operation: %s
CORE-10010​
Message
The clustering key boundary is not properly specified. Operation: %s
CORE-10011​
Message
The start clustering key is not properly specified. Operation: %s
CORE-10012​
Message
The end clustering key is not properly specified. Operation: %s
CORE-10013​
Message
Orderings are not properly specified. Operation: %s
CORE-10014​
Message
The specified ordering column is not found. Ordering: %s, Operation: %s
CORE-10015​
Message
The condition is not properly specified. Operation: %s
CORE-10016​
Message
The table does not exist. Table: %s
CORE-10017​
Message
The column value is not properly specified. Column: %s, Operation: %s
CORE-10018​
Message
The mutations are empty
CORE-10019​
Message
Mutations that span multiple partitions are not supported. Mutations: %s
CORE-10020​
Message
The partition key is not properly specified. Operation: %s
CORE-10021​
Message
The clustering key is not properly specified. Operation: %s
CORE-10022​
Message
This feature is not supported in the ScalarDB Community edition
CORE-10023​
Message
This condition is not allowed for the PutIf operation. Condition: %s
CORE-10024​
Message
This condition is not allowed for the DeleteIf operation. Condition: %s
CORE-10025​
Message
Operator must be LIKE or NOT_LIKE. Operator: %s
CORE-10026​
Message
An escape character must be a string of a single character or an empty string
CORE-10027​
Message
The LIKE pattern must not be null
CORE-10028​
Message
The LIKE pattern must not include only an escape character
CORE-10029​
Message
The LIKE pattern must not end with an escape character
CORE-10030​
Message
The column %s does not exist
CORE-10031​
Message
This operation is not supported when getting records of a database without using an index
CORE-10032​
Message
This operation is not supported when getting records of a database by using an index
CORE-10033​
Message
This operation is not supported when scanning all the records of a database or scanning records of a database by using an index
CORE-10034​
Message
This operation is supported only when scanning records of a database by using an index
CORE-10035​
Message
This operation is not supported when scanning records of a database by using an index
CORE-10036​
Message
This operation is supported only when scanning all the records of a database
CORE-10037​
Message
This operation is supported only when no conditions are specified at all. If you want to modify the condition, please use clearConditions() to remove all existing conditions first
CORE-10038​
Message
One or more columns must be specified.
CORE-10039​
Message
One or more partition keys must be specified.
CORE-10040​
Message
The column definition must be specified since %s is specified as a partition key
CORE-10041​
Message
The column definition must be specified since %s is specified as a clustering key
CORE-10042​
Message
Invalid ID specified. ID: %d
CORE-10043​
Message
The transaction is not active. Status: %s
CORE-10044​
Message
The transaction has already been committed or rolled back. Status: %s
CORE-10045​
Message
The transaction has not been prepared. Status: %s
CORE-10046​
Message
The transaction has not been prepared or validated. Status: %s
CORE-10047​
Message
The transaction already exists
CORE-10048​
Message
A transaction associated with the specified transaction ID is not found. The transaction might have expired
CORE-10049​
Message
%s is the system namespace name
CORE-10050​
Message
The namespace already exists. Namespace: %s
CORE-10051​
Message
The namespace does not exist. Namespace: %s
CORE-10052​
Message
The table already exists. Table: %s
CORE-10053​
Message
The namespace is not empty. Namespace: %s; Tables in the namespace: %s
CORE-10054​
Message
The column does not exist. Table: %s; Column: %s
CORE-10055​
Message
The index already exists. Table: %s; Column: %s
CORE-10056​
Message
The index does not exist. Table: %s; Column: %s
CORE-10057​
Message
The column already exists. Table: %s; Column: %s
CORE-10058​
Message
The operation does not have the target namespace or table name. Operation: %s
CORE-10059​
Message
The specified value of the property '%s' is not a number. Value: %s
CORE-10060​
Message
The specified value of the property '%s' is not a boolean. Value: %s
CORE-10061​
Message
Reading the file failed. File: %s
CORE-10062​
Message
The property 'scalar.db.cross_partition_scan.enabled' must be set to true to use cross-partition scan with filtering or ordering
CORE-10063​
Message
This column value is out of range for BigInt. Value: %s
CORE-10064​
Message
This type is not supported. Name: %s, Type: %s
CORE-10065​
Message
Storage '%s' is not found
CORE-10066​
Message
Transaction manager '%s' is not found
CORE-10067​
Message
Cross-partition scan with filtering or ordering is not supported in Cassandra
CORE-10068​
Message
Please use scan() for non-exact match selection. Operation: %s
CORE-10069​
Message
Import-related functionality is not supported in Cassandra
CORE-10070​
Message
The %s network strategy does not exist
CORE-10071​
Message
The property 'scalar.db.contact_port' must be greater than or equal to zero
CORE-10072​
Message
Cross-partition scan with filtering or ordering is not supported in Cosmos DB
CORE-10073​
Message
The BLOB type is not supported for clustering keys in Cosmos DB. Column: %s
CORE-10074​
Message
Import-related functionality is not supported in Cosmos DB
CORE-10075​
Message
The property 'scalar.db.contact_points' must not be empty
CORE-10076​
Message
Cosmos DB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BLOB type in conditions. Mutation: %s
CORE-10077​
Message
The specified consistency level is not supported. Consistency level: %s
CORE-10078​
Message
0x00 bytes are not accepted in BLOB values in DESC order
CORE-10079​
Message
Cannot encode a Text value that contains '\u0000'
CORE-10080​
Message
Cross-partition scan with filtering or ordering is not supported in DynamoDB
CORE-10081​
Message
An index column cannot be set to null or an empty value for Text or Blob in DynamoDB. Operation: %s
CORE-10082​
Message
DynamoDB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BOOLEAN type in conditions. Mutation: %s
CORE-10083​
Message
Nested multi-storage definitions are not supported. Storage: %s
CORE-10084​
Message
Storage not found. Storage: %s
CORE-10085​
Message
The namespace name is not acceptable. Namespace: %s
CORE-10086​
Message
The table name is not acceptable. Table: %s
CORE-10087​
Message
Importing tables is not allowed in the RDB engine. RDB engine: %s
CORE-10088​
Message
The %s table must have a primary key
CORE-10089​
Message
The RDB engine is not supported. JDBC connection URL: %s
CORE-10090​
Message
Data type %s(%d) is not supported: %s
CORE-10091​
Message
Data type %s is not supported: %s
CORE-10092​
Message
Getting a transaction state is not supported in JDBC transactions
CORE-10093​
Message
Rolling back a transaction is not supported in JDBC transactions
CORE-10094​
Message
Coordinator tables already exist
CORE-10095​
Message
Coordinator tables do not exist
CORE-10096​
Message
The namespace %s is reserved. Any operations on this namespace are not allowed
CORE-10097​
Message
Mutating transaction metadata columns is not allowed. Table: %s; Column: %s
CORE-10098​
Message
A %s condition is not allowed on Put operations
CORE-10099​
Message
A %s condition is not allowed on Delete operations
CORE-10100​
Message
The condition is not allowed to target transaction metadata columns. Column: %s
CORE-10101​
Message
The column '%s' is reserved as transaction metadata
CORE-10102​
Message
Non-primary key columns with the 'before_' prefix, '%s', are reserved as transaction metadata
CORE-10103​
Message
Put cannot have a condition when the target record is unread and implicit pre-read is disabled. Please read the target record beforehand or enable implicit pre-read: %s
CORE-10104​
Message
Writing already-deleted data is not allowed
CORE-10105​
Message
Getting data neither in the read set nor the delete set is not allowed
CORE-10106​
Message
Reading already-written data is not allowed
CORE-10107​
Message
The transaction is not validated. When using the EXTRA_READ serializable strategy, you need to call validate() before calling commit()
CORE-10108​
Message
DynamoDB cannot batch more than 100 mutations at once
CORE-10109​
Message
The partition keys of the table %s.%s were modified, but altering partition keys is not supported
CORE-10110​
Message
The clustering keys of the table %s.%s were modified, but altering clustering keys is not supported
CORE-10111​
Message
The clustering ordering of the table %s.%s were modified, but altering clustering ordering is not supported
CORE-10112​
Message
The column %s of the table %s.%s has been deleted. Column deletion is not supported when altering a table
CORE-10113​
Message
The data type of the column %s of the table %s.%s was modified, but altering data types is not supported
CORE-10114​
Message
Specifying the '--schema-file' option is required when using the '--repair-all' option
CORE-10115​
Message
Specifying the '--schema-file' option is required when using the '--alter' option
CORE-10116​
Message
Specifying the '--schema-file' option is required when using the '--import' option
CORE-10117​
Message
Specifying the '--coordinator' option with the '--import' option is not allowed. Create Coordinator tables separately
CORE-10118​
Message
Reading the configuration file failed. File: %s
CORE-10119​
Message
Reading the schema file failed. File: %s
CORE-10120​
Message
Parsing the schema JSON failed. Details: %s
CORE-10121​
Message
The table name must contain the namespace and the table. Table: %s
CORE-10122​
Message
The partition key must be specified. Table: %s
CORE-10123​
Message
Invalid clustering-key format. The clustering key must be in the format of 'column_name' or 'column_name ASC/DESC'. Table: %s; Clustering key: %s
CORE-10124​
Message
Columns must be specified. Table: %s
CORE-10125​
Message
Invalid column type. Table: %s; Column: %s; Type: %s
CORE-10145​
Message
The value of the column %s in the primary key contains an illegal character. Primary-key columns must not contain any of the following characters in Cosmos DB: ':', '/', '\', '#', '?'. Value: %s
CORE-2xxxx status codes​
CORE-20000​
Message
No mutation was applied
CORE-20001​
Message
Logging failed in the batch
CORE-20002​
Message
The operation failed in the batch with type %s
CORE-20003​
Message
An error occurred in the batch. Details: %s
CORE-20004​
Message
A Paxos phase in the CAS operation failed
CORE-20005​
Message
The learn phase in the CAS operation failed
CORE-20006​
Message
A simple write operation failed
CORE-20007​
Message
An error occurred in the mutation. Details: %s
CORE-20008​
Message
A RetryWith error occurred in the mutation. Details: %s
CORE-20009​
Message
A transaction conflict occurred in the mutation. Details: %s
CORE-20010​
Message
A transaction conflict occurred in the mutation. Details: %s
CORE-20011​
Message
A conflict occurred. Please try restarting the transaction
CORE-20012​
Message
The %s condition of the %s operation is not satisfied. Targeting column(s): %s
CORE-20013​
Message
The record being prepared already exists
CORE-20014​
Message
A conflict occurred when preparing records
CORE-20015​
Message
The committing state in the coordinator failed. The transaction has been aborted
CORE-20016​
Message
A conflict occurred during implicit pre-read
CORE-20017​
Message
This record needs to be recovered
CORE-20018​
Message
The record does not exist, so the %s condition is not satisfied
CORE-20019​
Message
The record exists, so the %s condition is not satisfied
CORE-20020​
Message
The condition on the column '%s' is not satisfied
CORE-20021​
Message
Reading empty records might cause a write skew anomaly, so the transaction has been aborted for safety purposes
CORE-20022​
Message
An anti-dependency was found. The transaction has been aborted
CORE-3xxxx status codes​
CORE-30000​
Message
Creating the namespace failed. Namespace: %s
CORE-30001​
Message
Dropping the namespace failed. Namespace: %s
CORE-30002​
Message
Creating the table failed. Table: %s
CORE-30003​
Message
Dropping the table failed. Table: %s
CORE-30004​
Message
Truncating the table failed. Table: %s
CORE-30005​
Message
Creating the index failed. Table: %s, Column: %s
CORE-30006​
Message
Dropping the index failed. Table: %s, Column: %s
CORE-30007​
Message
Getting the table metadata failed. Table: %s
CORE-30008​
Message
Getting the table names in the namespace failed. Namespace: %s
CORE-30009​
Message
Checking the namespace existence failed. Namespace: %s
CORE-30010​
Message
Checking the table existence failed. Table: %s
CORE-30011​
Message
Checking the index existence failed. Table: %s; Column: %s
CORE-30012​
Message
Repairing the namespace failed. Namespace: %s
CORE-30013​
Message
Repairing the table failed. Table: %s
CORE-30014​
Message
Adding a new column to the table failed. Table: %s; Column: %s; ColumnType: %s
CORE-30015​
Message
Getting the namespace names failed
CORE-30016​
Message
Getting the table metadata of the table being imported failed. Table: %s
CORE-30017​
Message
Importing the table failed. Table: %s
CORE-30018​
Message
Adding the raw column to the table failed. Table: %s; Column: %s; ColumnType: %s
CORE-30019​
Message
Upgrading the ScalarDB environment failed
CORE-30020​
Message
Something wrong because WriteType is neither CAS nor SIMPLE
CORE-30021​
Message
An error occurred in the selection. Details: %s
CORE-30022​
Message
An error occurred in the mutation. Details: %s
CORE-30023​
Message
An error occurred in the selection. Details: %s
CORE-30024​
Message
An error occurred in the mutation. Details: %s
CORE-30025​
Message
An error occurred in the selection. Details: %s
CORE-30026​
Message
An error occurred in the mutation. Details: %s
CORE-30027​
Message
An error occurred in the selection. Details: %s
CORE-30028​
Message
Fetching the next result failed
CORE-30029​
Message
Rolling back the transaction failed
CORE-30030​
Message
Committing the transaction failed
CORE-30031​
Message
The Get operation failed
CORE-30032​
Message
The Scan operation failed
CORE-30033​
Message
The Put operation failed
CORE-30034​
Message
The Delete operation failed
CORE-30035​
Message
Beginning a transaction failed
CORE-30036​
Message
Preparing records failed
CORE-30037​
Message
Validation failed
CORE-30038​
Message
Executing implicit pre-read failed
CORE-30039​
Message
The Get operation failed
CORE-30040​
Message
The Scan operation failed
CORE-30041​
Message
Rollback failed because the transaction has already been committed
CORE-30042​
Message
Rollback failed
CORE-4xxxx status codes​
CORE-40000​
Message
Rolling back the transaction failed
CORE-40001​
Message
Committing state failed with NoMutationException, but the coordinator status does not exist
CORE-40002​
Message
The state cannot be retrieved
CORE-40003​
Message
The coordinator status is unknown
CORE-40004​
Message
Aborting state failed with NoMutationException, but the coordinator status does not exist