Sign in

v52

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

Check if a table exists

Check if table id exists.

This operation should behave exactly like DescribeTable, except it does not contain a response body.

REST NAMESPACE ONLY REST namespace conveys the result through the HTTP status code with no response body. The REST response maps to the TableExistsResponse model as follows:

  • a 200 response means the table exists; a 404 response means it does not
  • response headers map to context via the header. prefix (see the Context schema)

For DirectoryNamespace implementation, a table exists if either:

  • The table has Lance data versions (regular table created with CreateTable)
  • A .lance-reserved file exists in the table directory (declared table created with DeclareTable)
post/v1/table/{id}/exists

Path parameters

idstring required

string identifier of an object in a namespace, following the Lance Namespace spec. When the value is equal to the delimiter, it represents the root namespace. For example, v1/namespace/$/list performs a ListNamespace on the root namespace.

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:TableExistsRequest: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"}
idstring[]
versioninteger

Version of the table to check existence. If not specified, server should resolve it to the latest version.

Example request

{
  "identity": {
    "api_key": "api_key",
    "auth_token": "auth_token"
  },
  "context": {
    "key": "context"
  },
  "id": [
    "id",
    "id"
  ],
  "version": 0
}

Response

Success, no content