Move idempotency_records schema to v4 and add H2 support #3386
+359
−30
Conversation
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
6 tasks
singhpk234
reviewed
Jan 8, 2026
singhpk234
approved these changes
Jan 8, 2026
Contributor
singhpk234
left a comment
singhpk234
left a comment
There was a problem hiding this comment.
LGTM, thanks @huaxingao
github-project-automation
bot
moved this from PRs In Progress
to Ready to merge
in Basic Kanban Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Moves the idempotency_records table definition and indexes from schema-v3 to schema-v4 for Postgres, and adds the matching idempotency_records table and realm‑scoped expiry index to H2 schema-v4. This keeps both JDBC backends aligned on the v4 schema for idempotency persistence
Checklist
CHANGELOG.md(if needed)site/content/in-dev/unreleased(if needed)