Single file drivers¶
Chunked storage drivers¶
- json KeyValueStoreBackedChunkDriver : object¶
Common options supported by all chunked storage drivers.
- Required members:¶
- Optional members:¶
rank : integer[
Specifies the rank of the TensorStore.
transformis also specified, the input rank must match. Otherwise, the rank constraint applies to the driver directly.
- schema : Schema¶
Specifies constraints on the schema.
When opening an existing array, specifies constraints on the existing schema; opening will fail if the constraints do not match. Any soft constraints specified in the
chunk_layoutare ignored. When creating a new array, a suitable schema will be selected automatically based on the specified schema constraints in combination with any driver-specific constraints.
path : string =
This is joined as an additional
"/"-separated path component after any
pathmember directly within
kvstore. This is supported for backwards compatibility only; the
KvStore.pathmember should be used instead.
- open : boolean¶
create : boolean =
delete_existing : boolean =
assume_metadata : boolean =
Skip reading the metadata if possible. Instead, just assume any necessary metadata based on constraints in the spec, using the same defaults for any unspecified metadata as when creating a new TensorStore. Requires that
This option can lead to data corruption if the assumed metadata does not match the stored metadata, or multiple concurrent writers use different assumed metadata.
cache_pool : ContextResource =
data_copy_concurrency : ContextResource =
recheck_cached_metadata : CacheRevalidationBound =
Time after which cached metadata is assumed to be fresh. Cached metadata older than the specified time is revalidated prior to use. The metadata is used to check the bounds of every read or write operation.
truemeans that the metadata will be revalidated prior to every read or write operation. With the default value of
"open", any cached metadata is revalidated when the TensorStore is opened but is not rechecked for each read or write operation.
recheck_cached_data : CacheRevalidationBound =
Time after which cached data is assumed to be fresh. Cached data older than the specified time is revalidated prior to being returned from a read operation. Partial chunk writes are always consistent regardless of the value of this option.
The default value of
truemeans that cached data is revalidated on every read. To enable in-memory data caching, you must both specify a
cache_poolwith a non-zero
total_bytes_limitand also specify
"open", or an explicit time bound for
- rank : integer[
json CacheRevalidationBound :
Determines under what circumstances cached data is revalidated.
- One of:¶
Revalidate cached data at every operation.
Assume cached data is always fresh and never revalidate.
Revalidate cached data older than the time at which the TensorStore was opened.
Revalidate cached data older than the specified time in seconds since the unix epoch.