Sign in

v52

latestOpenAPI 3.1.1Apache 2.0raw.githubusercontent.com2026-08-0354155395.9 KB
Table
Metadata

Atomically create versions for multiple tables

Atomically create new version entries for multiple tables.

This operation is atomic: either all table versions are created successfully, or none are created. If any version creation fails (e.g., due to conflict), the entire batch operation fails.

Each entry in the request specifies the table identifier and version details. This supports put_if_not_exists semantics for each version entry.

post/v1/table/version/batch-create

Query parameters

delimiterstring

An optional delimiter of the string identifier, following the Lance Namespace spec. When not specified, the $ delimiter must be used.

Request body

{"stackTrail":"components:schemas:BatchCreateTableVersionsRequest:properties:context","oasType":"schema","type":"unknown","description":"Arbitrary context as key-value pairs.\nHow to use the context is custom to the specific implementation.\n\nOn a request, it carries caller-provided context to the implementation.\nOn a response, it carries implementation-provided context back to the caller.\n\nREST NAMESPACE ONLY\nContext entries are mapped to and from HTTP headers using the `header.` prefix:\n- On a request, any entry whose key starts with `header.` is sent as an HTTP\n request header with the prefix stripped. For example, the entry\n `{\"header.Authorization\": \"Bearer abc\"}` is sent as the request header\n `Authorization: Bearer abc`.\n- On a response, every HTTP response header is returned as an entry whose key is the\n header name prefixed with `header.`. For example, the response header\n `x-request-id: abc123` is returned as the entry `{\"header.x-request-id\": \"abc123\"}`.\n"}

Example request

{
  "entries": [
    {
      "naming_scheme": "V2",
      "metadata": {
        "key": "metadata"
      },
      "manifest_path": "manifest_path",
      "manifest_size": 0,
      "id": [
        "id",
        "id"
      ],
      "e_tag": "e_tag",
      "version": 0,
      "branch": "branch"
    },
    {
      "naming_scheme": "V2",
      "metadata": {
        "key": "metadata"
      },
      "manifest_path": "manifest_path",
      "manifest_size": 0,
      "id": [
        "id",
        "id"
      ],
      "e_tag": "e_tag",
      "version": 0,
      "branch": "branch"
    }
  ],
  "identity": {
    "api_key": "api_key",
    "auth_token": "auth_token"
  },
  "context": {
    "key": "context"
  }
}

Response

Result of atomically creating table versions

{"stackTrail":"components:schemas:BatchCreateTableVersionsResponse:properties:context","oasType":"schema","type":"unknown","description":"Arbitrary context as key-value pairs.\nHow to use the context is custom to the specific implementation.\n\nOn a request, it carries caller-provided context to the implementation.\nOn a response, it carries implementation-provided context back to the caller.\n\nREST NAMESPACE ONLY\nContext entries are mapped to and from HTTP headers using the `header.` prefix:\n- On a request, any entry whose key starts with `header.` is sent as an HTTP\n request header with the prefix stripped. For example, the entry\n `{\"header.Authorization\": \"Bearer abc\"}` is sent as the request header\n `Authorization: Bearer abc`.\n- On a response, every HTTP response header is returned as an entry whose key is the\n header name prefixed with `header.`. For example, the response header\n `x-request-id: abc123` is returned as the entry `{\"header.x-request-id\": \"abc123\"}`.\n"}
transaction_idstring

Optional transaction identifier

Example response

{
  "transaction_id": "transaction_id",
  "versions": [
    {
      "metadata": {
        "key": "metadata"
      },
      "manifest_path": "manifest_path",
      "timestamp_millis": 1,
      "manifest_size": 0,
      "e_tag": "e_tag",
      "version": 0
    },
    {
      "metadata": {
        "key": "metadata"
      },
      "manifest_path": "manifest_path",
      "timestamp_millis": 1,
      "manifest_size": 0,
      "e_tag": "e_tag",
      "version": 0
    }
  ],
  "context": {
    "key": "context"
  }
}