Data API error codes

Column names must be unique in the table schema.

The command attempted to add a field with a name that already exists in the type definition.

The command attempted to add an index that already exists in the keyspace schema.

The command attempted to add a table that already exists in the keyspace schema.

The command attempted to add a type that already exists in the keyspace schema.

The command attempted to add a column that was previously dropped, and the database rejected it because the new type is incompatible with the type retained in dropped-column metadata.

The command attempted to add columns with unsupported data types to the table schema.

Index function entries can not apply to map column when analyze options are specified.

Columns that are indexed cannot be dropped from the table schema.

Primary key columns cannot be dropped from the table schema.

The command attempted to drop a type that is used by tables.

The command attempted to drop columns that are not in the table schema.

The command attempted to drop an index that is not in the keyspace schema.

The command attempted to drop a table that is not in the keyspace schema.

The command attempted to drop a type that is not in the keyspace schema.

Columns can only have the vectorize configuration dropped if they use the vector column type.

The command attempted to drop vectorize configuration from columns that are not in the table schema.

The command attempted to lexical filter on column that is not text-indexed.

The command attempted to lexical sort on column that is not indexed.

The command attempted to lexical sort column along with skip option set.

The command attempted to rename a field that is not defined in the named type.

The command used a sort clause with more than one vectorize sort, only one vectorize sort is allowed.

The command used a sort clause with more than one vector sort, only one vector sort is allowed.

The command used a sort clause with a special (lexical/vector/vectorize) sort combined with one or more other sort expressions:

The command attempted to sort using columns that are not in the table schema.

The command attempted to vector sort vector columns and other non vector columns.

Columns can only be vectorized if they use the vector column type.

The command attempted to vectorize sort on a column that is not of vector type.

Vectorize sort can only be used with columns that have a vectorize configuration.

The command attempted to vectorize columns that are not in the table schema.

The command attempted to vector sort vector columns that are not indexed.

The command attempted to vector sort on a column that is not of vector type.

The command attempted to vector sort vector columns with a mismatched vector dimension.

The command attempted to vector sort columns with a limit that exceeds the maximum allowed.

The command attempted to vector sort columns along with skip option set.

Column [column] doesn’t exist in the table.

Column data type not provided or format invalid in the definition.

Command '[command]' does not accept options but some were included.

Command field '[field]' not recognized: [message].

Command field '[field]' value [value] not valid: [message].

Command '[command]' is not a [commandType] recognized by Data API.

The filter uses $lt, $gt, $lte, $gte (comparison filters) on columns that, while indexed, are still inefficient to filter on.

The command attempted to create or alter a collection or table to use a AI Model that has been marked as deprecated. Deprecated models are only supported by the API for existing use and will later be removed.

A deprecated command was used, it may still be used but will be removed in future releases.

Cannot insert the document: a document already exists with given '_id' ([id]).

The replace document and document resolved using filter have different '_id’s: [replaceId] (replace document) vs. [matchedId] (document that filter matches).

See also Replace a document.

Collection '[table]' does not have embedding service configured: cannot vectorize data.

The command attempted to use an AI Model that has been marked as end of life. End of life models cannot be used in any way. Collections or tables that use the model must be recreated as data such as embeddings is not transferrable.

Collection '[collectionName]' already exists but with settings different from ones passed with 'createCollection' command.

The command attempted to create an collection, however the the name of one of the indexes needed for the collection conflicts with an existing index in the database.

Attempt to create new collection failed: table '[tableName]' already exists and it is not a valid Data API collection.

Filter has [fieldCount] fields, exceeds maximum allowed ([maxFieldCount]).

Collection field '_id' is never indexed so filtering can only be done using operators '$eq' or '$in', not '[operator]'.

Unsupported filter clause: [message].

Command included more than one '_id' equals filter clauses, which is not supported: use '$in' operator instead.

Collection path '[path]' is not indexed: cannot filter on that path.

See also Selective indexing.

Unsupported filter data type: [message].

Unsupported [message].

Field '$hybrid' cannot be used with '$lexical', '$vector', or '$vectorize'.

Unknown sub-field(s) for '$hybrid' field: [errorMessage].

Unsupported JSON value type for '$hybrid' sub-field: [errorMessage].

Unsupported JSON value type for '$hybrid' field: [errorMessage].

The filter only specified columns from the primary key, but did not specify the full primary key for the table.

Only values that are supported by the column data type can be included when inserting a document into a table.

'createCollection' command referenced unrecognized field(s): [message]

'createCollection' command option(s) invalid: [message]

Only values that are supported by the column data type can be included when filtering.

Command has an invalid format for index creation column.

'createCollection' indexing definition invalid: [errorMessage].

Provided index configuration is not valid: [reason].

Keyspace used is not valid: [keyspace]

Command has an invalid filter, [detailedReason].

The command requires a filter on the primary key that specifies all of the partitioning keys, and the partition sort keys in order.

The command has invalid usage of $push operator, [reason].

The command attempted to use unsupported JSON expression [jsonExpr] (type [jsonType]) for sort clause.

The reranking service override in the findAndRerank command is invalid.

Only values that are supported by the column data type can be included when updating.

'$vector' and '$vectorize' cannot be used together in same document[extraDesc].

User defined type name is not valid: [udtName].

Unable to parse vectorize configuration, schema invalid for field '[field]' (of table '[keyspace].[table]').

Unable to parse vectorize configuration, schema invalid for table '[keyspace].[table]'.

Invalid $vectorize value: [errorMessage].

The command attempted to update or find using $vector, using a vector that has a length different to the declared '$vector' dimension for the Collection.

The command attempted to use unsupported JSON type ([jsonType]) for vector or vectorize sort.

Sorting uses skip option, performing as in memory sort

The command used columns in the sort clause that are all part of the partition sorting, however the sort clause was missing some of the partition sorting columns.

The command used columns in the sort clause that are not part of the partition sorting, and so the query was sorted in memory.

The command used columns in the sort clause that are all part of the partition sorting, however the sort clause used a different column order to the partition sorting.

The command wants to perform sort, however the filter clause does not have partition keys correctly restricted.

The command attempted to insert or update the $lexical field with content that exceeds the maximum allowed length.

The command attempted to enable lexical search functionality but lexical search is not supported by this database.

Lexical content can only be added and filtering and sort only be used on collections for which Lexical feature is enabled.

MCP feature is not enabled for this database.

The alterTable command must contain at least one operation to alter the table schema, such as adding or dropping columns.

The alterType command must contain at least one operation to alter the type schema, such as adding or renaming fields.

The command did not include an authorization token in the request headers.

The dimension is required for vector columns if the embedding service is not specified.

The type definition must have at least one field.

Update and delete commands for tables require a filter.

The updateOne and `deleteOne`commands can only filter using the fully specify the primary key for the table.

The filter includes columns that are not indexed.

The table definition must have at least one partition key.

All primary key columns must be provided when inserting a document into a table.

The findAndRerank command is missing the text to use as the query with the reranking model.

The command did not include any non empty update operations to change the columns in the table.

The filter uses $ne (not equals) on columns that, while indexed, are still inefficient to filter on using not equals.

The filter uses $nin on columns that, while indexed, are still inefficient to filter on.

The command used in-memory sorting which has a limit of [maxLimit] [unit]s.

Primary key definition provided is incorrect.

The Data API failed to detect that the query generated by the command was inefficient due to a lack of primary key or index usage, and so it was retried after failing.

Request not valid JSON, problem: [errorMessage].

Request is valid JSON but has a structural mismatch: [errorMessage].

Reranking feature is not enabled for this database.

No authentication key provided for reranking provider: In order to rerank, please provide the reranking API key.

Reranking provider client error: [errorMessage].

Reranking provider rate-limited: [errorMessage].

Reranking provider server error: [errorMessage].

Reranking provider returned an unexpected response: [errorMessage].

Reranking service type unavailable: [errorMessage].

Bad binary vector value to shred: [errorMessage].

Bad type for '_id' field: [errorMessage].

Bad value for '_id' field: [errorMessage].

Bad $lexical value to shred: [errorMessage].

Bad document type to shred: document must be a JSON Object, instead got a JSON [documentType].

Bad $vector value to shred: [errorMessage].

Bad JSON Extension value to shred: [errorMessage].

Document field name not valid: [errorMessage].

Bad $vector value: cannot be empty Array.

Bad $vector value: needs to be an array containing only Numbers but has a [nodeType] value ([nodeValue]).

Document size limitation violated: [errorMessage].

Sort clause used by command not valid.

Path '[path]' used in sort clause not valid: [problem].

Collection field '[path]' is not indexed: cannot sort using it.

Value used for sort expression on path '[path]' not valid: [problem].

Cannot create collection '[table]': the maximum number of collections per database is [collectionMaxCount], database already has [collectionCount].

The command attempted to create an collection, however the number of indexes in the database has reached the maximum allowed.

Authentication failed for request due to invalid token.

The command is not authorized to perform the action on the database.

The command tried to get a Collection or Table [table] that does not exist in the Keyspace [keyspace].

The column definition used a data type that is not known.

The command attempted to create an index on a column that is not in the table schema.

The command attempted to create an index using an unknown type.

The command tried to use a Keyspace that does not exist in the Database.

The column used to partition by are not present in the table schema.

The columns used for partition sorting are not present in the table schema.

The column definition used the short hand for the data type, which only supports primitive data types.

Only columns defined in the table schema can be included when inserted a document into a table.

Only columns defined in the table schema can be filtered on.

Only columns defined in the table schema can be updated.

Only columns defined in the table schema can be included in the projection.

The column uses a user defined type that is not known.

The command attempted to create an vector index using a metric that is not known by the API.

The command attempted to create an vector index using a vector source model that is not known by the API.

The command is not supported by collections in the API.

Only supported column types can be included when inserting a document into a table.

Only column types supported by the API can be filtered on.

Only supported column types can be included when updating columns in a table.

Only supported column types can be included when reading from a table.

Filtering using the comparison operations ($lt, $gt, $lte, $gte) is not supported against duration column types.

Request sent with unsupported 'Content-Type' header value.

The column definition used unsupported data types for the table creation.

Filtering is only supported on primitive data types such as text not on container types such as list, set, map, or vector.

The Filtering using the non $eq filter operations can select more than one row, and so cannot be used with the updateOne and deleteOne commands as they can only modify one row.

The command attempted to create an index on a column that uses a data type not supported for indexing.

The command attempted to create an index on a column that is frozen.

The command attempted to create an index using an unsupported type.

The command attempted to create a text index using an unsupported JSON value type.

The command attempted to create a list column that used an unsupported type for the value.

The command attempted to create a map column that used unsupported types for either the key or value.

The Update or delete commands can only filter using columns that are part of the primary key.

The command included multiple update operations that attempted to change the same column. For example, attempting to both $set and $unset a column.

Pagination is not supported when the data is sorted in-memory.

Unsupported projection definition JSON value: must be Object, was [projectionValueType].

Unsupported projection parameter: [errorMessage].

The findAndRerank is not enabled for the collection, and a reranking service override was not provided with the command.

The command attempted to create a [schemaType] with a name that is not supported.

The command attempted to create a set column that used an unsupported type for the value.

The command attempted to sort a delete command running against a table.

The command attempted to sort a update command running against a table.

The command is not supported by tables in the API.

The command attempted to create an index that specified text analysis on a column that uses a data type not supported for text analysis.

The command attempted to create a text index on a column that is not a text or ascii type.

The command attempted to create a user defined type with field definitions that use unsupported types.

Unsupported update data type: [errorMessage].

Columns in the primary key for the table cannot be updated.

Unsupported update operation: [errorMessage].

The command included update operations that are not supported by tables.

Unsupported update operation modifier: [errorMessage].

Unsupported update operation parameter: [errorMessage].

Unsupported update operation path: [errorMessage].

Unsupported target JSON value for update operation: [errorMessage].

Only update operators that are supported by the column type can be used in the update clause.

The command used the update operator: [operator].

The command used the update operator: [operator].

The command used the update operator: [operator].

The command used the update operator: [operator].

A request can include only one unique combination of provider, model, and dimension for vectorization.

The command attempted to use vectorize sort (keyword '$vectorize' or '$hybrid') against a collection that does not have vectorize enabled.

Vectorize can only be used with columns that have a vectorize configuration.

Vectorize can only be used with columns that have a vectorize configuration.

Vectorize can onl be performed on columns that have a vectorize configuration.

The command attempted to create a vector column that used an unsupported configuration.

The command attempted to create a vector index on a column that is not a vector type.

The command attempted to vector sort against a collection that does not have vectors enabled.

Invalid credential name for vectorize, with error: [errorMessage].

Vectorize feature is not available in the environment.

Vector search is not enabled for collection: [keyspace].[table].

Vector embedding property '$vector' length too big: [length] (max [maxLength]).

Unknown vector search function name: '[function]'.

Unrecognized vector search source model name: [errorMessage].

Zero filters were provided in the filter for this query.