メインコンテンツまでスキップ
バージョン: 3.13

ScalarDB エラーコード

注記

このページは英語版のページが機械翻訳されたものです。英語版との間に矛盾または不一致がある場合は、英語版を正としてください。

このページでは、ScalarDB のエラーコードの一覧を示します。

エラーコードのクラスと説明

クラス説明
CORE-1xxxxユーザーエラーカテゴリのエラー
CORE-2xxxx同時実行エラーカテゴリのエラー
CORE-3xxxx内部エラーカテゴリのエラー
CORE-4xxxx不明なトランザクションステータスエラーカテゴリのエラー

CORE-1xxxx ステータスコード

CORE-10000

メッセージ

Only a single-column index is supported. Operation: %s

CORE-10001

メッセージ

The column of the specified index key is not indexed. Operation: %s

CORE-10002

メッセージ

The index key is not properly specified. Operation: %s

CORE-10003

メッセージ

Clustering keys cannot be specified when using an index. Operation: %s

CORE-10004

メッセージ

Orderings cannot be specified when using an index. Operation: %s

CORE-10005

メッセージ

The limit cannot be negative. Operation: %s

CORE-10006

メッセージ

Cross-partition scan is not enabled. Operation: %s

CORE-10007

メッセージ

Cross-partition scan ordering is not enabled. Operation: %s

CORE-10008

メッセージ

Cross-partition scan filtering is not enabled. Operation: %s

CORE-10009

メッセージ

The specified projection is not found. Projection: %s, Operation: %s

CORE-10010

メッセージ

The clustering key boundary is not properly specified. Operation: %s

CORE-10011

メッセージ

The start clustering key is not properly specified. Operation: %s

CORE-10012

メッセージ

The end clustering key is not properly specified. Operation: %s

CORE-10013

メッセージ

Orderings are not properly specified. Operation: %s

CORE-10014

メッセージ

The specified ordering column is not found. Ordering: %s, Operation: %s

CORE-10015

メッセージ

The condition is not properly specified. Operation: %s

CORE-10016

メッセージ

The table does not exist. Table: %s

CORE-10017

メッセージ

The column value is not properly specified. Column: %s, Operation: %s

CORE-10018

メッセージ

The mutations are empty

CORE-10019

メッセージ

Mutations that span multiple partitions are not supported. Mutations: %s

CORE-10020

メッセージ

The partition key is not properly specified. Operation: %s

CORE-10021

メッセージ

The clustering key is not properly specified. Operation: %s

CORE-10022

メッセージ

This feature is not supported in the ScalarDB Community edition

CORE-10023

メッセージ

This condition is not allowed for the PutIf operation. Condition: %s

CORE-10024

メッセージ

This condition is not allowed for the DeleteIf operation. Condition: %s

CORE-10025

メッセージ

Operator must be LIKE or NOT_LIKE. Operator: %s

CORE-10026

メッセージ

An escape character must be a string of a single character or an empty string

CORE-10027

メッセージ

The LIKE pattern must not be null

CORE-10028

メッセージ

The LIKE pattern must not include only an escape character

CORE-10029

メッセージ

The LIKE pattern must not end with an escape character

CORE-10030

メッセージ

The column %s does not exist

CORE-10031

メッセージ

This operation is not supported when getting records of a database without using an index

CORE-10032

メッセージ

This operation is not supported when getting records of a database by using an index

CORE-10033

メッセージ

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

メッセージ

This operation is supported only when scanning records of a database by using an index

CORE-10035

メッセージ

This operation is not supported when scanning records of a database by using an index

CORE-10037

メッセージ

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 first

CORE-10038

メッセージ

One or more columns must be specified.

CORE-10039

メッセージ

One or more partition keys must be specified.

CORE-10040

メッセージ

The column definition must be specified since %s is specified as a partition key

CORE-10041

メッセージ

The column definition must be specified since %s is specified as a clustering key

CORE-10042

メッセージ

Invalid ID specified. ID: %d

CORE-10043

メッセージ

The transaction is not active. Status: %s

CORE-10044

メッセージ

The transaction has already been committed or rolled back. Status: %s

CORE-10045

メッセージ

The transaction has not been prepared. Status: %s

CORE-10046

メッセージ

The transaction has not been prepared or validated. Status: %s

CORE-10047

メッセージ

The transaction already exists

CORE-10048

メッセージ

A transaction associated with the specified transaction ID is not found. The transaction might have expired

CORE-10049

メッセージ

%s is the system namespace name

CORE-10050

メッセージ

The namespace already exists. Namespace: %s

CORE-10051

メッセージ

The namespace does not exist. Namespace: %s

CORE-10052

メッセージ

The table already exists. Table: %s

CORE-10053

メッセージ

The namespace is not empty. Namespace: %s; Tables in the namespace: %s

CORE-10054

メッセージ

The column does not exist. Table: %s; Column: %s

CORE-10055

メッセージ

The index already exists. Table: %s; Column: %s

CORE-10056

メッセージ

The index does not exist. Table: %s; Column: %s

CORE-10057

メッセージ

The column already exists. Table: %s; Column: %s

CORE-10058

メッセージ

The operation does not have the target namespace or table name. Operation: %s

CORE-10059

メッセージ

The specified value of the property '%s' is not a number. Value: %s

CORE-10060

メッセージ

The specified value of the property '%s' is not a boolean. Value: %s

CORE-10061

メッセージ

Reading the file failed. File: %s

CORE-10062

メッセージ

The property 'scalar.db.cross_partition_scan.enabled' must be set to true to use cross-partition scan with filtering or ordering

CORE-10063

メッセージ

This column value is out of range for BigInt. Value: %s

CORE-10064

メッセージ

This type is not supported. Name: %s, Type: %s

CORE-10065

メッセージ

Storage '%s' is not found

CORE-10066

メッセージ

Transaction manager '%s' is not found

CORE-10068

メッセージ

Please use scan() for non-exact match selection. Operation: %s

CORE-10069

メッセージ

Import-related functionality is not supported in Cassandra

CORE-10070

メッセージ

The %s network strategy does not exist

CORE-10071

メッセージ

The property 'scalar.db.contact_port' must be greater than or equal to zero

CORE-10073

メッセージ

The BLOB type is not supported for clustering keys in Cosmos DB. Column: %s

CORE-10074

メッセージ

Import-related functionality is not supported in Cosmos DB

CORE-10075

メッセージ

The property 'scalar.db.contact_points' must not be empty

CORE-10076

メッセージ

Cosmos DB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BLOB type in conditions. Mutation: %s

CORE-10077

メッセージ

The specified consistency level is not supported. Consistency level: %s

CORE-10078

メッセージ

0x00 bytes are not accepted in BLOB values in DESC order

CORE-10079

メッセージ

Cannot encode a Text value that contains '\u0000'

CORE-10081

メッセージ

An index column cannot be set to null or an empty value for Text or Blob in DynamoDB. Operation: %s

CORE-10082

メッセージ

DynamoDB supports only EQ, NE, IS_NULL, and IS_NOT_NULL operations for the BOOLEAN type in conditions. Mutation: %s

CORE-10083

メッセージ

Nested multi-storage definitions are not supported. Storage: %s

CORE-10084

メッセージ

Storage not found. Storage: %s

CORE-10085

メッセージ

The namespace name is not acceptable. Namespace: %s

CORE-10086

メッセージ

The table name is not acceptable. Table: %s

CORE-10087

メッセージ

Importing tables is not allowed in the RDB engine. RDB engine: %s

CORE-10088

メッセージ

The %s table must have a primary key

CORE-10089

メッセージ

The RDB engine is not supported. JDBC connection URL: %s

CORE-10090

メッセージ

Data type %s(%d) is not supported: %s

CORE-10091

メッセージ

Data type %s is not supported: %s

CORE-10092

メッセージ

Getting a transaction state is not supported in JDBC transactions

CORE-10093

メッセージ

Rolling back a transaction is not supported in JDBC transactions

CORE-10094

メッセージ

Coordinator tables already exist

CORE-10095

メッセージ

Coordinator tables do not exist

CORE-10096

メッセージ

The namespace %s is reserved. Any operations on this namespace are not allowed

CORE-10097

メッセージ

Mutating transaction metadata columns is not allowed. Table: %s; Column: %s

CORE-10098

メッセージ

A %s condition is not allowed on Put operations

CORE-10099

メッセージ

A %s condition is not allowed on Delete operations

CORE-10100

メッセージ

The condition is not allowed to target transaction metadata columns. Column: %s

CORE-10101

メッセージ

The column '%s' is reserved as transaction metadata

CORE-10102

メッセージ

Non-primary key columns with the 'before_' prefix, '%s', are reserved as transaction metadata

CORE-10103

メッセージ

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

メッセージ

Writing already-deleted data is not allowed

CORE-10105

メッセージ

Getting data neither in the read set nor the delete set is not allowed

CORE-10106

メッセージ

Reading already-written data is not allowed

CORE-10107

メッセージ

The transaction is not validated. When using the EXTRA_READ serializable strategy, you need to call validate() before calling commit()

CORE-10108

メッセージ

DynamoDB cannot batch more than 100 mutations at once

CORE-10109

メッセージ

The partition keys of the table %s.%s were modified, but altering partition keys is not supported

CORE-10110

メッセージ

The clustering keys of the table %s.%s were modified, but altering clustering keys is not supported

CORE-10111

メッセージ

The clustering ordering of the table %s.%s were modified, but altering clustering ordering is not supported

CORE-10112

メッセージ

The column %s of the table %s.%s has been deleted. Column deletion is not supported when altering a table

CORE-10113

メッセージ

The data type of the column %s of the table %s.%s was modified, but altering data types is not supported

CORE-10114

メッセージ

Specifying the '--schema-file' option is required when using the '--repair-all' option

CORE-10115

メッセージ

Specifying the '--schema-file' option is required when using the '--alter' option

CORE-10116

メッセージ

Specifying the '--schema-file' option is required when using the '--import' option

CORE-10117

メッセージ

Specifying the '--coordinator' option with the '--import' option is not allowed. Create Coordinator tables separately

CORE-10118

メッセージ

Reading the configuration file failed. File: %s

CORE-10119

メッセージ

Reading the schema file failed. File: %s

CORE-10120

メッセージ

Parsing the schema JSON failed. Details: %s

CORE-10121

メッセージ

The table name must contain the namespace and the table. Table: %s

CORE-10122

メッセージ

The partition key must be specified. Table: %s

CORE-10123

メッセージ

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

メッセージ

Columns must be specified. Table: %s

CORE-10125

メッセージ

Invalid column type. Table: %s; Column: %s; Type: %s

CORE-10126

メッセージ

The mutation type is not supported. Only the Put or Delete type is supported. Mutation: %s

CORE-10127

メッセージ

This condition is not allowed for the UpdateIf operation. Condition: %s

CORE-10128

メッセージ

Cross-partition scan with ordering is not supported in Cassandra

CORE-10129

メッセージ

Cross-partition scan with ordering is not supported in Cosmos DB

CORE-10130

メッセージ

Cross-partition scan with ordering is not supported in DynamoDB

CORE-10131

メッセージ

The directory '%s' does not have write permissions. Please ensure that the current user has write access to the directory.

CORE-10132

メッセージ

Failed to create the directory '%s'. Please check if you have sufficient permissions and if there are any file system restrictions. Details: %s

CORE-10133

メッセージ

Directory path cannot be null or empty.

CORE-10134

メッセージ

No file extension was found on the provided file name %s.

CORE-10135

メッセージ

Invalid file extension: %s. Allowed extensions are: %s

CORE-10136

メッセージ

Getting a transaction state is not supported in single CRUD operation transactions

CORE-10137

メッセージ

Rolling back a transaction is not supported in single CRUD operation transactions

CORE-10138

メッセージ

Multiple mutations are not supported in single CRUD operation transactions

CORE-10139

メッセージ

Beginning a transaction is not allowed in single CRUD operation transactions

CORE-10140

メッセージ

Resuming a transaction is not allowed in single CRUD operation transactions

CORE-10141

メッセージ

Using the group commit feature on the Coordinator table with a two-phase commit interface is not allowed

CORE-10142

メッセージ

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 first

CORE-10145

メッセージ

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 ステータスコード

CORE-20000

メッセージ

No mutation was applied

CORE-20001

メッセージ

Logging failed in the batch

CORE-20002

メッセージ

The operation failed in the batch with type %s

CORE-20003

メッセージ

An error occurred in the batch. Details: %s

CORE-20004

メッセージ

A Paxos phase in the CAS operation failed

CORE-20005

メッセージ

The learn phase in the CAS operation failed

CORE-20006

メッセージ

A simple write operation failed

CORE-20007

メッセージ

An error occurred in the mutation. Details: %s

CORE-20008

メッセージ

A RetryWith error occurred in the mutation. Details: %s

CORE-20009

メッセージ

A transaction conflict occurred in the mutation. Details: %s

CORE-20010

メッセージ

A transaction conflict occurred in the mutation. Details: %s

CORE-20011

メッセージ

A conflict occurred. Please try restarting the transaction. Details: %s

CORE-20012

メッセージ

The %s condition of the %s operation is not satisfied. Targeting column(s): %s

CORE-20013

メッセージ

The record being prepared already exists

CORE-20014

メッセージ

A conflict occurred when preparing records

CORE-20015

メッセージ

The committing state in the coordinator failed. The transaction has been aborted

CORE-20016

メッセージ

A conflict occurred during implicit pre-read

CORE-20017

メッセージ

This record needs to be recovered

CORE-20018

メッセージ

The record does not exist, so the %s condition is not satisfied

CORE-20019

メッセージ

The record exists, so the %s condition is not satisfied

CORE-20020

メッセージ

The condition on the column '%s' is not satisfied

CORE-20021

メッセージ

Reading empty records might cause a write skew anomaly, so the transaction has been aborted for safety purposes

CORE-20022

メッセージ

An anti-dependency was found. The transaction has been aborted

CORE-20023

メッセージ

A transaction conflict occurred in the Insert operation

CORE-20024

メッセージ

The %s condition of the %s operation is not satisfied. Targeting column(s): %s

CORE-20025

メッセージ

A transaction conflict occurred in the Insert operation

CORE-3xxxx ステータスコード

CORE-30000

メッセージ

Creating the namespace failed. Namespace: %s

CORE-30001

メッセージ

Dropping the namespace failed. Namespace: %s

CORE-30002

メッセージ

Creating the table failed. Table: %s

CORE-30003

メッセージ

Dropping the table failed. Table: %s

CORE-30004

メッセージ

Truncating the table failed. Table: %s

CORE-30005

メッセージ

Creating the index failed. Table: %s, Column: %s

CORE-30006

メッセージ

Dropping the index failed. Table: %s, Column: %s

CORE-30007

メッセージ

Getting the table metadata failed. Table: %s

CORE-30008

メッセージ

Getting the table names in the namespace failed. Namespace: %s

CORE-30009

メッセージ

Checking the namespace existence failed. Namespace: %s

CORE-30010

メッセージ

Checking the table existence failed. Table: %s

CORE-30011

メッセージ

Checking the index existence failed. Table: %s; Column: %s

CORE-30012

メッセージ

Repairing the namespace failed. Namespace: %s

CORE-30013

メッセージ

Repairing the table failed. Table: %s

CORE-30014

メッセージ

Adding a new column to the table failed. Table: %s; Column: %s; ColumnType: %s

CORE-30015

メッセージ

Getting the namespace names failed

CORE-30016

メッセージ

Getting the table metadata of the table being imported failed. Table: %s

CORE-30017

メッセージ

Importing the table failed. Table: %s

CORE-30018

メッセージ

Adding the raw column to the table failed. Table: %s; Column: %s; ColumnType: %s

CORE-30019

メッセージ

Upgrading the ScalarDB environment failed

CORE-30020

メッセージ

Something wrong because WriteType is neither CAS nor SIMPLE

CORE-30021

メッセージ

An error occurred in the selection. Details: %s

CORE-30022

メッセージ

An error occurred in the mutation. Details: %s

CORE-30023

メッセージ

An error occurred in the selection. Details: %s

CORE-30024

メッセージ

An error occurred in the mutation. Details: %s

CORE-30025

メッセージ

An error occurred in the selection. Details: %s

CORE-30026

メッセージ

An error occurred in the mutation. Details: %s

CORE-30027

メッセージ

An error occurred in the selection. Details: %s

CORE-30028

メッセージ

Fetching the next result failed

CORE-30029

メッセージ

Rolling back the transaction failed. Details: %s

CORE-30030

メッセージ

Committing the transaction failed. Details: %s

CORE-30031

メッセージ

The Get operation failed. Details: %s

CORE-30032

メッセージ

The Scan operation failed. Details: %s

CORE-30033

メッセージ

The Put operation failed. Details: %s

CORE-30034

メッセージ

The Delete operation failed. Details: %s

CORE-30035

メッセージ

Beginning a transaction failed. Details: %s

CORE-30036

メッセージ

Preparing records failed

CORE-30037

メッセージ

Validation failed

CORE-30038

メッセージ

Executing implicit pre-read failed

CORE-30039

メッセージ

Reading a record from the underlying storage failed

CORE-30040

メッセージ

Scanning records from the underlying storage failed

CORE-30041

メッセージ

Rollback failed because the transaction has already been committed

CORE-30042

メッセージ

Rollback failed

CORE-30043

メッセージ

The Insert operation failed. Details: %s

CORE-30044

メッセージ

The Upsert operation failed. Details: %s

CORE-30045

メッセージ

The Update operation failed. Details: %s

CORE-4xxxx ステータスコード

CORE-40000

メッセージ

Rolling back the transaction failed. Details: %s

CORE-40001

メッセージ

Committing state failed with NoMutationException, but the coordinator status does not exist

CORE-40002

メッセージ

The state cannot be retrieved

CORE-40003

メッセージ

The coordinator status is unknown

CORE-40004

メッセージ

Aborting state failed with NoMutationException, but the coordinator status does not exist