You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: