Atomically create new version entries for multiple tables.
This operation is atomic: either all table versions are created successfully, or none are created. If any version creation fails (e.g., due to conflict), the entire batch operation fails.
Each entry in the request specifies the table identifier and version details.
This supports put_if_not_exists semantics for each version entry.
The access token received from the authorization server in the OAuth 2.0 flow.
An optional delimiter of the string identifier, following the Lance Namespace spec.
When not specified, the $ delimiter must be used.
Request to atomically create new version entries for multiple tables. The operation is atomic: all versions are created or none are.
List of table version entries to create atomically
Identity information of a request.
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.
Result of atomically creating table versions