Skip to content
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

[Discuss] Support different stores for different projects in one single feast-serving container #30

Open
randxie opened this issue Apr 28, 2021 · 2 comments
Assignees

Comments

@randxie
Copy link

randxie commented Apr 28, 2021

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.

@woop
Copy link
Member

woop commented Apr 28, 2021

@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?

@woop woop closed this as completed Apr 28, 2021
@woop woop reopened this Apr 28, 2021
@woop woop self-assigned this Apr 28, 2021
@randxie
Copy link
Author

randxie commented Apr 28, 2021

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants