chore(testapp): use default TTL for datastream entity caches - #105
Merged
bpapillon merged 1 commit intoSep 5, 2026
Merged
Conversation
In replicator mode the replicator writes companies to Redis without a TTL. track() writes the company back with the datastream cache TTL, so the 2s E2E TTL expired the entry and the replicator skipped later partial updates. Matches the Go testapp, which leaves the datastream caches on the 24h default.
bpapillon
marked this pull request as ready for review
September 5, 2026 00:14
schematic-bot
approved these changes
Sep 5, 2026
bpapillon
deleted the
bpapillon/sch-7065-replicator-mode-missing-entities
branch
September 5, 2026 00:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the python / replicator E2E failures (SCH-7065).
The testapp gave the datastream entity caches the 2s E2E TTL. In replicator mode the replicator owns those Redis entries and writes them without a TTL; when the SDK wrote the company back after track(), the entry picked up the 2s TTL and expired, and the replicator then skipped every later partial update for that company ("No cached resource for partial company"). The Go testapp leaves these caches on the SDK default (24h); do the same here. The short TTL still applies to the flag-check cache.