List all versions (commits) of table id with their metadata.
Use descending=true to guarantee versions are returned in descending order (latest to oldest).
Otherwise, the ordering is implementation-defined.
REST NAMESPACE ONLY
REST namespace does not use a request body for this operation.
The ListTableVersionsRequest information is passed in the following way:
id: pass through path parameter of the same namepage_token: pass through query parameter of the same namelimit: pass through query parameter of the same namedescending: pass through query parameter of the same nameThe access token received from the authorization server in the OAuth 2.0 flow.
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.
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.
When true, versions are guaranteed to be returned in descending order (latest to oldest). When false or not specified, the ordering is implementation-defined.
List of table versions
List of table versions. When descending=true, guaranteed to be ordered from latest to oldest.
Otherwise, ordering is implementation-defined.
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.