Skip to content

fix(redis): persist no-expiration TTL updates - #2689

Open
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/redis-persist-no-expiration
Open

fix(redis): persist no-expiration TTL updates#2689
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/redis-persist-no-expiration

Conversation

@HandSonic

Copy link
Copy Markdown
Contributor

Summary

  • Send Redis PERSIST when an existing key changes from a positive TTL to no expiration.
  • Add regression coverage for TTL command selection.

Tests

  • RedisScriptExecutorUpdateTest: 7/7
  • Redis plugin test suite: 58/58
  • Redis plugin package build

Fixes #2681

@HandSonic
HandSonic requested a review from openai0229 as a code owner August 12, 2026 01:00
@openai0229 openai0229 moved this to In Review in Chat2DB Community Aug 12, 2026
@HandSonic
HandSonic force-pushed the fix/redis-persist-no-expiration branch 2 times, most recently from e747220 to 2ece48c Compare August 12, 2026 17:34
@HandSonic
HandSonic force-pushed the fix/redis-persist-no-expiration branch from 2ece48c to 730dea4 Compare August 19, 2026 19:40
openai0229
openai0229 previously approved these changes Aug 20, 2026

@openai0229 openai0229 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The TTL transition logic is correct: a positive TTL still emits , and changing an existing non-permanent key to emits without affecting type-replacement flows. Tests cover the command selection. Approved.

@openai0229
openai0229 dismissed their stale review August 20, 2026 03:45

Superseded by a corrected review because shell quoting corrupted the submitted text.

@openai0229 openai0229 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The TTL transition logic is correct: a positive TTL still emits EXPIRE, and changing an existing non-permanent key to -1 emits PERSIST without affecting type-replacement flows. Tests cover the command selection. Approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

bug(redis): removing a key TTL does not persist the key

2 participants