| tags | displayed_sidebar | |||
|---|---|---|---|---|
|
docsEnglish |
This page provides a list of error codes in ScalarDB Core.
| 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 |
Message
Only a single-column index is supported. Operation: %sMessage
The column of the specified index key is not indexed. Operation: %sMessage
The index key is not properly specified. Operation: %sMessage
Clustering keys cannot be specified when using an index. Operation: %sMessage
Orderings cannot be specified when using an index. Operation: %sMessage
The limit cannot be negative. Operation: %sMessage
Cross-partition scan is not enabled. Operation: %sMessage
Cross-partition scan ordering is not enabled. Operation: %sMessage
Cross-partition scan filtering is not enabled. Operation: %sMessage
The specified projection is not found. Projection: %s, Operation: %sMessage
The clustering key boundary is not properly specified. Operation: %sMessage
The start clustering key is not properly specified. Operation: %sMessage
The end clustering key is not properly specified. Operation: %sMessage
Orderings are not properly specified. Operation: %sMessage
The specified ordering column is not found. Ordering: %s, Operation: %sMessage
The condition is not properly specified. Operation: %sMessage
The table does not exist. Table: %sMessage
The column value is not properly specified. Column: %s, Operation: %sMessage
The mutations are emptyMessage
Mutations that span multiple partitions are not supported. Mutations: %sMessage
The partition key is not properly specified. Operation: %sMessage
The clustering key is not properly specified. Operation: %sMessage
The authentication and authorization feature is not enabled. To use this feature, you must enable it. Note that this feature is supported only in the ScalarDB Enterprise editionMessage
This condition is not allowed for the PutIf operation. Condition: %sMessage
This condition is not allowed for the DeleteIf operation. Condition: %sMessage
Operator must be LIKE or NOT_LIKE. Operator: %sMessage
An escape character must be a string of a single character or an empty stringMessage
The LIKE pattern must not be nullMessage
The LIKE pattern must not include only an escape characterMessage
The LIKE pattern must not end with an escape characterMessage
The column %s does not existMessage
This operation is not supported when getting records of a database without using an indexMessage
This operation is not supported when getting records of a database by using an indexMessage
This operation is not supported when scanning all the records of a database or scanning records of a database by using an indexMessage
This operation is supported only when scanning records of a database by using an indexMessage
This operation is not supported when scanning records of a database by using an indexMessage
This operation is supported only when no conditions are specified. If you want to modify a condition, please use clearConditions() to remove all existing conditions firstMessage
One or more columns must be specified.Message
One or more partition keys must be specified.Message
The column definition must be specified since %s is specified as a partition keyMessage
The column definition must be specified since %s is specified as a clustering keyMessage
Invalid ID specified. ID: %dMessage
The transaction is not active. Status: %sMessage
The transaction has already been committed or rolled back. Status: %sMessage
The transaction has not been prepared. Status: %sMessage
The transaction has not been prepared or validated. Status: %sMessage
The transaction already existsMessage
A transaction associated with the specified transaction ID is not found. The transaction might have expiredMessage
%s is the system namespace nameMessage
The namespace already exists. Namespace: %sMessage
The namespace does not exist. Namespace: %sMessage
The table already exists. Table: %sMessage
The namespace is not empty. Namespace: %s; Tables in the namespace: %sMessage
The column does not exist. Table: %s; Column: %sMessage
The index already exists. Table: %s; Column: %sMessage
The index does not exist. Table: %s; Column: %sMessage
The column already exists. Table: %s; Column: %sMessage
The operation does not have the target namespace or table name. Operation: %sMessage
The specified value of the property '%s' is not a number. Value: %sMessage
The specified value of the property '%s' is not a boolean. Value: %sMessage
Reading the file failed. File: %sMessage
The property 'scalar.db.cross_partition_scan.enabled' must be set to true to use cross-partition scan with filtering or orderingMessage
This column value is out of range for BigInt. Value: %sMessage
This type is not supported. Name: %s, Type: %sMessage
Storage '%s' is not foundMessage
Transaction manager '%s' is not foundMessage
Please use scan() for non-exact match selection. Operation: %sMessage
Import-related functionality is not supported in CassandraMessage
The %s network strategy does not existMessage
The property 'scalar.db.contact_port' must be greater than or equal to zeroMessage
The BLOB type is not supported for clustering keys in Cosmos DB. Column: %sMessage
Import-related functionality is not supported in Cosmos DBMessage
The property 'scalar.db.contact_points' must not be emptyMessage
Cosmos DB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BLOB type in conditions. Mutation: %sMessage
The specified consistency level is not supported. Consistency level: %sMessage
0x00 bytes are not accepted in BLOB values in DESC orderMessage
Cannot encode a Text value that contains '\u0000'Message
An index column cannot be set to null or an empty value for Text or Blob in DynamoDB. Operation: %sMessage
DynamoDB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BOOLEAN type in conditions. Mutation: %sMessage
Nested multi-storage definitions are not supported. Storage: %sMessage
Storage not found. Storage: %sMessage
The namespace name is not acceptable. Namespace: %sMessage
The table name is not acceptable. Table: %sMessage
Importing tables is not allowed in the RDB engine. RDB engine: %sMessage
The %s table must have a primary keyMessage
The RDB engine is not supported. JDBC connection URL: %sMessage
Data type %s(%d) is not supported: %sMessage
Data type %s is not supported: %sMessage
Getting a transaction state is not supported in JDBC transactionsMessage
Rolling back a transaction is not supported in JDBC transactionsMessage
Coordinator tables already existMessage
Coordinator tables do not existMessage
The namespace %s is reserved. Any operations on this namespace are not allowedMessage
Mutating transaction metadata columns is not allowed. Table: %s; Column: %sMessage
A %s condition is not allowed on Put operationsMessage
A %s condition is not allowed on Delete operationsMessage
The condition is not allowed to target transaction metadata columns. Column: %sMessage
The column '%s' is reserved as transaction metadataMessage
Non-primary key columns with the 'before_' prefix, '%s', are reserved as transaction metadataMessage
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: %sMessage
Writing already-deleted data is not allowedMessage
Getting data neither in the read set nor the delete set is not allowedMessage
Reading already-written data is not allowedMessage
The transaction is not validated. When using the EXTRA_READ serializable strategy, you need to call validate() before calling commit()Message
DynamoDB cannot batch more than 100 mutations at onceMessage
The partition keys of the table %s.%s were modified, but altering partition keys is not supportedMessage
The clustering keys of the table %s.%s were modified, but altering clustering keys is not supportedMessage
The clustering ordering of the table %s.%s were modified, but altering clustering ordering is not supportedMessage
The column %s of the table %s.%s has been deleted. Column deletion is not supported when altering a tableMessage
The data type of the column %s of the table %s.%s was modified, but altering data types is not supportedMessage
Specifying the '--schema-file' option is required when using the '--repair-all' optionMessage
Specifying the '--schema-file' option is required when using the '--alter' optionMessage
Specifying the '--schema-file' option is required when using the '--import' optionMessage
Specifying the '--coordinator' option with the '--import' option is not allowed. Create Coordinator tables separatelyMessage
Reading the configuration file failed. File: %sMessage
Reading the schema file failed. File: %sMessage
Parsing the schema JSON failed. Details: %sMessage
The table name must contain the namespace and the table. Table: %sMessage
The partition key must be specified. Table: %sMessage
Invalid clustering-key format. The clustering key must be in the format of 'column_name' or 'column_name ASC/DESC'. Table: %s; Clustering key: %sMessage
Columns must be specified. Table: %sMessage
Invalid column type. Table: %s; Column: %s; Type: %sMessage
The mutation type is not supported. Only the Put or Delete type is supported. Mutation: %sMessage
This condition is not allowed for the UpdateIf operation. Condition: %sMessage
Cross-partition scan with ordering is not supported in CassandraMessage
Cross-partition scan with ordering is not supported in Cosmos DBMessage
Cross-partition scan with ordering is not supported in DynamoDBMessage
The directory '%s' does not have write permissions. Please ensure that the current user has write access to the directory.Message
Failed to create the directory '%s'. Please check if you have sufficient permissions and if there are any file system restrictions. Details: %sMessage
Directory path cannot be null or empty.Message
No file extension was found on the provided file name %s.Message
Invalid file extension: %s. Allowed extensions are: %sMessage
Getting a transaction state is not supported in single CRUD operation transactionsMessage
Rolling back a transaction is not supported in single CRUD operation transactionsMessage
Multiple mutations are not supported in single CRUD operation transactionsMessage
Beginning a transaction is not allowed in single CRUD operation transactionsMessage
Resuming a transaction is not allowed in single CRUD operation transactionsMessage
Using the group commit feature on the Coordinator table with a two-phase commit interface is not allowedMessage
This operation is supported only when no conditions are specified. If you want to modify a condition, please use clearConditions() to remove all existing conditions firstMessage
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: %sMessage
Inserting already-written data is not allowedMessage
Deleting already-inserted data is not allowedMessage
Invalid key: Column %s does not exist in the table %s in namespace %s.Message
Invalid base64 encoding for blob value for column %s in table %s in namespace %sMessage
Invalid number specified for column %s in table %s in namespace %sMessage
Method null argument not allowedMessage
No mutation was appliedMessage
Logging failed in the batchMessage
The operation failed in the batch with type %sMessage
An error occurred in the batch. Details: %sMessage
A Paxos phase in the CAS operation failedMessage
The learn phase in the CAS operation failedMessage
A simple write operation failedMessage
An error occurred in the mutation. Details: %sMessage
A RetryWith error occurred in the mutation. Details: %sMessage
A transaction conflict occurred in the mutation. Details: %sMessage
A transaction conflict occurred in the mutation. Details: %sMessage
A conflict occurred. Please try restarting the transaction. Details: %sMessage
The %s condition of the %s operation is not satisfied. Targeting column(s): %sMessage
The record being prepared already existsMessage
A conflict occurred when preparing recordsMessage
The committing state in the coordinator failed. The transaction has been abortedMessage
A conflict occurred during implicit pre-readMessage
This record needs to be recoveredMessage
The record does not exist, so the %s condition is not satisfiedMessage
The record exists, so the %s condition is not satisfiedMessage
The condition on the column '%s' is not satisfiedMessage
Reading empty records might cause a write skew anomaly, so the transaction has been aborted for safety purposesMessage
An anti-dependency was found. The transaction has been abortedMessage
A transaction conflict occurred in the Insert operationMessage
The %s condition of the %s operation is not satisfied. Targeting column(s): %sMessage
A transaction conflict occurred in the Insert operationMessage
Creating the namespace failed. Namespace: %sMessage
Dropping the namespace failed. Namespace: %sMessage
Creating the table failed. Table: %sMessage
Dropping the table failed. Table: %sMessage
Truncating the table failed. Table: %sMessage
Creating the index failed. Table: %s, Column: %sMessage
Dropping the index failed. Table: %s, Column: %sMessage
Getting the table metadata failed. Table: %sMessage
Getting the table names in the namespace failed. Namespace: %sMessage
Checking the namespace existence failed. Namespace: %sMessage
Checking the table existence failed. Table: %sMessage
Checking the index existence failed. Table: %s; Column: %sMessage
Repairing the namespace failed. Namespace: %sMessage
Repairing the table failed. Table: %sMessage
Adding a new column to the table failed. Table: %s; Column: %s; ColumnType: %sMessage
Getting the namespace names failedMessage
Getting the table metadata of the table being imported failed. Table: %sMessage
Importing the table failed. Table: %sMessage
Adding the raw column to the table failed. Table: %s; Column: %s; ColumnType: %sMessage
Upgrading the ScalarDB environment failedMessage
Something wrong because WriteType is neither CAS nor SIMPLEMessage
An error occurred in the selection. Details: %sMessage
An error occurred in the mutation. Details: %sMessage
An error occurred in the selection. Details: %sMessage
An error occurred in the mutation. Details: %sMessage
An error occurred in the selection. Details: %sMessage
An error occurred in the mutation. Details: %sMessage
An error occurred in the selection. Details: %sMessage
Fetching the next result failedMessage
Rolling back the transaction failed. Details: %sMessage
Committing the transaction failed. Details: %sMessage
The Get operation failed. Details: %sMessage
The Scan operation failed. Details: %sMessage
The Put operation failed. Details: %sMessage
The Delete operation failed. Details: %sMessage
Beginning a transaction failed. Details: %sMessage
Preparing records failedMessage
Validation failedMessage
Executing implicit pre-read failedMessage
Reading a record from the underlying storage failedMessage
Scanning records from the underlying storage failedMessage
Rollback failed because the transaction has already been committedMessage
Rollback failedMessage
The Insert operation failed. Details: %sMessage
The Upsert operation failed. Details: %sMessage
The Update operation failed. Details: %sMessage
Rolling back the transaction failed. Details: %sMessage
Committing state failed with NoMutationException, but the coordinator status does not existMessage
The state cannot be retrievedMessage
The coordinator status is unknownMessage
Aborting state failed with NoMutationException, but the coordinator status does not exist