-
Notifications
You must be signed in to change notification settings - Fork 334
fix: Include connectionId in metadata cache key #1272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: c6d0eda The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3cc0a9f to
0fec8ef
Compare
E2E Test Results✅ All tests passed • 25 passed • 3 skipped • 230s
|
PR Review: Include connectionId in metadata cache key✅ No critical issues found. The changes are well-structured and consistently applied across all cache keys in the metadata layer: What was changed:
Quality observations:
This is a solid bug fix that properly isolates metadata by connection. |
0fec8ef to
24e5e1a
Compare
dhable
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great
Closes HDX-2573
This PR adds connection ID to the metadata cache key, to ensure that metadata is not shared across tables with the same name in different connections.
For example, previously when switching between otel_logs tables in different connections, filter values would not reload:
Screen.Recording.2025-10-15.at.4.26.43.PM.mov
Now they will:
Screen.Recording.2025-10-15.at.4.25.45.PM.mov