Skip to content

Fix Vector Sets losing expiration after migration - #2179

Merged
kevin-montrose merged 8 commits into
mainfrom
users/kmontrose/vectorSetExpiration
Sep 30, 2026
Merged

kevin-montrose merged 8 commits into
mainfrom
users/kmontrose/vectorSetExpiration

Conversation

@kevin-montrose

Copy link
Copy Markdown
Contributor

Part of stabilizing for Vector Sets.

Migration did not check for, serialize, or restore expiration data - similarly, replication after migration did not serialize or restore expiration data.

Copilot AI balanced review requested due to automatic review settings September 28, 2026 19:28
@kevin-montrose kevin-montrose mentioned this pull request Sep 28, 2026
18 of 19 tasks

Copilot AI 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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@kevin-montrose
kevin-montrose merged commit cdf966b into main Sep 30, 2026
331 of 333 checks passed
@kevin-montrose
kevin-montrose deleted the users/kmontrose/vectorSetExpiration branch September 30, 2026 18:47
x@01 (x-at-01) added a commit to webc-fork/garnet that referenced this pull request Oct 4, 2026
…2187,microsoft#2188,microsoft#2189), Vector Sets expiration after migration (microsoft#2179), Vector Set RESP2/RESP3 contracts (microsoft#2184), AOF recovery hang + ScanCursor read-ahead + size-tracker fixes (microsoft#2181)
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.

3 participants