Skip to content

chore(testapp): use default TTL for datastream entity caches - #105

Merged
bpapillon merged 1 commit into
mainfrom
bpapillon/sch-7065-replicator-mode-missing-entities
Sep 5, 2026
Merged

chore(testapp): use default TTL for datastream entity caches#105
bpapillon merged 1 commit into
mainfrom
bpapillon/sch-7065-replicator-mode-missing-entities

Conversation

@bpapillon

Copy link
Copy Markdown
Collaborator

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.

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
bpapillon marked this pull request as ready for review September 5, 2026 00:14
@bpapillon
bpapillon requested a review from a team as a code owner September 5, 2026 00:14
@bpapillon
bpapillon merged commit 1b9c4fb into main Sep 5, 2026
4 checks passed
@bpapillon
bpapillon deleted the bpapillon/sch-7065-replicator-mode-missing-entities branch September 5, 2026 00:15
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