Sign in
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.

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 for a request as key-value pairs.\nHow to use the context is custom to the specific implementation.\n\nREST NAMESPACE ONLY\nContext entries are passed via HTTP headers using the naming convention\n`x-lance-ctx-<key>: <value>`. For example, a context entry\n`{\"trace_id\": \"abc123\"}` would be sent as the header `x-lance-ctx-trace_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

Changes