Sign in

v1

latestOpenAPI 3.1.1Apache 2.02026-07-2654130166.5 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

Request body

contextContext

Arbitrary context as key-value pairs. How to use the context is custom to the specific implementation.

On a request, it carries caller-provided context to the implementation. On a response, it carries implementation-provided context back to the caller.

REST NAMESPACE ONLY Context entries are mapped to and from HTTP headers using the header. prefix:

  • On a request, any entry whose key starts with header. is sent as an HTTP request header with the prefix stripped. For example, the entry {"header.Authorization": "Bearer abc"} is sent as the request header Authorization: Bearer abc.
  • On a response, every HTTP response header is returned as an entry whose key is the header name prefixed with header.. For example, the response header x-request-id: abc123 is returned as the entry {"header.x-request-id": "abc123"}.
idstring[]
versioninteger

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

Response

Success, no content