Skip to content

Timeseries: fix stale cache warmer doc comments - #512

Merged
apurvam merged 1 commit into
mainfrom
timeseries-warmer-doc-comment
Jul 20, 2026
Merged

Timeseries: fix stale cache warmer doc comments#512
apurvam merged 1 commit into
mainfrom
timeseries-warmer-doc-comment

Conversation

@apurvam

@apurvam apurvam commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

The CacheWarmerConfig doc comment still described the pre-#509 warmer — scanning recent time bucket key ranges through the storage reader as "a temporary workaround until SlateDB's CacheManager is available". #509 switched the implementation to drive SlateDB's cache manager (warm_sst over the SSTs backing recent buckets) but left the comments behind.

Comment-only change; cargo check -p opendata-timeseries passes.

🤖 Generated with Claude Code

The CacheWarmerConfig doc comment still described the original warmer
(scanning recent key ranges through the reader, "a temporary workaround
until SlateDB's CacheManager is available"). #509 switched the
implementation to drive SlateDB's cache manager but left the comments
behind. Update them to describe the current behavior.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@apurvam
apurvam merged commit 5f5c288 into main Jul 20, 2026
3 checks passed
@apurvam
apurvam deleted the timeseries-warmer-doc-comment branch July 20, 2026 23:42
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.

1 participant