Skip to content

feat(tensorstore): expose recheck_cached_data on TensorStoreConfig#406

Merged
srivarra merged 2 commits into
mainfrom
feat/tensorstore-recheck-cached-data
Apr 24, 2026
Merged

feat(tensorstore): expose recheck_cached_data on TensorStoreConfig#406
srivarra merged 2 commits into
mainfrom
feat/tensorstore-recheck-cached-data

Conversation

@edyoshikun
Copy link
Copy Markdown
Collaborator

Add the rechecked_cached_data and fowrad the kward into _ts_open in open_array, when it's explicitly set.

Add ``recheck_cached_data`` to ``TensorStoreConfig`` and forward it into
``ts.open`` in ``TensorStoreImplementation.open_array``. The option controls
whether cached chunk data is revalidated on every read (the TensorStore
driver default) or only at open time (``"open"``), which is the recommended
setting for long-running read-heavy workloads on networked filesystems
(NFS/VAST) where revalidation costs one stat/GETATTR per chunk per read.

``None`` (default) preserves existing behaviour by omitting the kwarg so
the TensorStore driver keeps its own default. ``True``, ``False``, and
``"open"`` are forwarded verbatim.

Covered by a parametrized test that monkey-patches ``_ts_open`` to assert
the kwarg reaches TensorStore for each configured value and is absent when
unset.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@edyoshikun edyoshikun requested a review from srivarra April 23, 2026 23:05
@edyoshikun edyoshikun marked this pull request as ready for review April 23, 2026 23:05
@edyoshikun
Copy link
Copy Markdown
Collaborator Author

@srivarra can we merge this to bump to 0.3.3 or alpha so we can pin on viscy?

@srivarra
Copy link
Copy Markdown
Collaborator

@edyoshikun yeah

@srivarra srivarra merged commit efff544 into main Apr 24, 2026
7 checks passed
@edyoshikun edyoshikun deleted the feat/tensorstore-recheck-cached-data branch April 24, 2026 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants