A valid request URL is required to generate request examples{
"results": [
{
"declare_table": {
"transaction_id": "<string>",
"location": "<string>",
"storage_options": {},
"properties": {
"owner": "Ralph",
"created_at": "1452120468"
},
"managed_versioning": true
},
"create_table_version": {
"transaction_id": "<string>",
"version": {
"version": 1,
"manifest_path": "<string>",
"manifest_size": 1,
"e_tag": "<string>",
"timestamp_millis": 123,
"metadata": {}
}
},
"delete_table_versions": {
"deleted_count": 1,
"transaction_id": "<string>"
},
"deregister_table": {
"transaction_id": "<string>",
"id": [
"<string>"
],
"location": "<string>",
"properties": {
"owner": "Ralph",
"created_at": "1452120468"
}
}
}
],
"transaction_id": "<string>"
}Atomically commit a batch of table operations. This is a generalized version
of BatchCreateTableVersions that supports mixed operation types within a
single atomic transaction at the metadata layer.
Supported operation types:
DeclareTable: Declare (reserve) a new tableCreateTableVersion: Create a new version entry for a tableDeleteTableVersions: Delete version ranges from a tableDeregisterTable: Deregister (soft-delete) a tableAll operations are committed atomically: either all succeed or none are applied.
A valid request URL is required to generate request examples{
"results": [
{
"declare_table": {
"transaction_id": "<string>",
"location": "<string>",
"storage_options": {},
"properties": {
"owner": "Ralph",
"created_at": "1452120468"
},
"managed_versioning": true
},
"create_table_version": {
"transaction_id": "<string>",
"version": {
"version": 1,
"manifest_path": "<string>",
"manifest_size": 1,
"e_tag": "<string>",
"timestamp_millis": 123,
"metadata": {}
}
},
"delete_table_versions": {
"deleted_count": 1,
"transaction_id": "<string>"
},
"deregister_table": {
"transaction_id": "<string>",
"id": [
"<string>"
],
"location": "<string>",
"properties": {
"owner": "Ralph",
"created_at": "1452120468"
}
}
}
],
"transaction_id": "<string>"
}Documentation Index
Fetch the complete documentation index at: https://docs.lancedb.com/llms.txt
Use this file to discover all available pages before exploring further.
The access token received from the authorization server in the OAuth 2.0 flow.
An optional delimiter of the string identifier, following the Lance Namespace spec.
When not specified, the $ delimiter must be used.
Request to atomically commit a batch of table operations.
This replaces BatchCreateTableVersionsRequest with a more general interface
that supports mixed operations (DeclareTable, CreateTableVersion,
DeleteTableVersions, DeregisterTable)
within a single atomic transaction at the metadata layer.
All operations are committed atomically: either all succeed or none are applied.
List of operations to commit atomically. Supported operation types: DeclareTable, CreateTableVersion, DeleteTableVersions, DeregisterTable.
Show child attributes
Identity information of a request.
Show child attributes
Arbitrary context for a request as key-value pairs. How to use the context is custom to the specific implementation.
REST NAMESPACE ONLY
Context entries are passed via HTTP headers using the naming convention
x-lance-ctx-<key>: <value>. For example, a context entry
{"trace_id": "abc123"} would be sent as the header x-lance-ctx-trace_id: abc123.
Show child attributes
Result of atomically committing a batch of mixed table operations
Response for a batch commit of table operations. Contains the results of each operation in the same order as the request.
Was this page helpful?