CreateTableVersionRequest

Request to create a new table version entry. This supports put_if_not_exists semantics, where the operation fails if the version already exists.

Properties

Name	Type	Description	Notes
identity	Identity		[optional]
context	Map<String, String>	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`.	[optional]
id	List<String>	The table identifier	[optional]
version	Long	Version number to create
manifestPath	String	Path to the manifest file for this version
manifestSize	Long	Size of the manifest file in bytes	[optional]
eTag	String	Optional ETag for the manifest file	[optional]
metadata	Map<String, String>	Optional metadata for the version	[optional]
namingScheme	String	The naming scheme used for manifest files in the `_versions/` directory. Known values: - `V1`: `_versions/{version}.manifest` - Simple version-based naming - `V2`: `_versions/{inverted_version}.manifest` - Zero-padded, reversed version number (uses `u64::MAX - version`) for O(1) lookup of latest version on object stores V2 is preferred for new tables as it enables efficient latest-version discovery without needing to list all versions.	[optional]