List all tables
List all tables across all namespaces.
REST NAMESPACE ONLY
REST namespace uses GET to perform this operation without a request body.
It passes in the ListAllTablesRequest information in the following way:
page_token: pass through query parameter of the same namelimit: pass through query parameter of the same namedelimiter: pass through query parameter of the same name
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
An optional delimiter of the string identifier, following the Lance Namespace spec.
When not specified, the $ delimiter must be used.
Pagination token from a previous request An opaque token that allows pagination for list operations (e.g. ListNamespaces).
For an initial request of a list operation, if the implementation cannot return all items in one response, or if there are more items than the page limit specified in the request, the implementation must return a page token in the response, indicating there are more results available.
After the initial request, the value of the page token from each response must be used as the page token value for the next request.
Caller must interpret either null,
missing value or empty string value of the page token from
the implementation's response as the end of the listing results.
Maximum number of items to return An inclusive upper bound of the number of results that a caller will receive.
Response
A list of tables
The list of names of all the tables under the connected namespace implementation. This should recursively list all the tables in all child namespaces. Each string in the list is the full identifier in string form.
An opaque token that allows pagination for list operations (e.g. ListNamespaces).
For an initial request of a list operation, if the implementation cannot return all items in one response, or if there are more items than the page limit specified in the request, the implementation must return a page token in the response, indicating there are more results available.
After the initial request, the value of the page token from each response must be used as the page token value for the next request.
Caller must interpret either null,
missing value or empty string value of the page token from
the implementation's response as the end of the listing results.