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
Move the discussion from slack to github issue for visibility.
We have a use case that require using different redis clusters for different projects, e.g. shared features can be placed in a shared redis cluster and team-specific features can be placed in team redis cluster. We will have a single request that read from multiple clusters.
If we think this is the direction moving forward, we can brainstorm implementation details here.
The text was updated successfully, but these errors were encountered:
@randxie thanks for creating this issue. One question: What do you mean across different projects? Do you mean a single request should be able to read from both different clusters and across projects? Meaning you want to do something like project.feature_table.feature? Or by project do you mean your internal company projects or use cases?
Sorry for the confusion, by project, I mean the project in Feast (project.feature_table.feature). We mapped project to team internally, where each project will have its own online store (redis cluster).
Move the discussion from slack to github issue for visibility.
We have a use case that require using different redis clusters for different projects, e.g. shared features can be placed in a shared redis cluster and team-specific features can be placed in team redis cluster. We will have a single request that read from multiple clusters.
If we think this is the direction moving forward, we can brainstorm implementation details here.
The text was updated successfully, but these errors were encountered: