Skip to content

Standardize Redis Key Prefix for User Lineage Context #7891

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

Open
tsdk02 opened this issue Apr 24, 2025 · 0 comments · Fixed by #7892 · May be fixed by #7903
Open

Standardize Redis Key Prefix for User Lineage Context #7891

tsdk02 opened this issue Apr 24, 2025 · 0 comments · Fixed by #7892 · May be fixed by #7903
Assignees

Comments

@tsdk02
Copy link
Contributor

tsdk02 commented Apr 24, 2025

Currently, the lineage context is cached in Redis using tenant-specific key prefixes (public_, public_v2_). This causes inconsistencies across V1 and V2 environments — especially during login/logout flows — as lineage context data becomes deployment-specific.

Need to introduce a new Redis connection helper that overrides the prefix with the global value from config (global).

@tsdk02 tsdk02 self-assigned this Apr 24, 2025
@tsdk02 tsdk02 linked a pull request Apr 24, 2025 that will close this issue
14 tasks
@tsdk02 tsdk02 reopened this Apr 25, 2025
@tsdk02 tsdk02 linked a pull request Apr 25, 2025 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant