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.

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

Error

A valid request URL is required to generate request examples

400

{
  "type": "/errors/bad-request",
  "title": "Malformed request",
  "status": 400,
  "detail": "",
  "instance": "/v1/namespaces"
}

Authorizations

OAuth2BearerAuthApiKeyAuth

Authorization · string · header · required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

id · string · 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

delimiter · string

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

Body

application/json

identity · object

Identity information of a request.

Show child attributes

context · object

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

id · string[]

version · integer<int64>

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

Required range: x >= 0

Response

200

Success, no content