[Discuss] Support different stores for different projects in one single feast-serving container
@woop is already working on this.
Since Apr 28, 2021.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- Java
- Stars
- 12
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from feast-dev/feast-java-old
-
feast-dev/feast-java-old#20 · 8 comments · 1 assignee ·
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
feast-dev/feast-java-old#6 · 5 comments · 1 reaction ·
All issues in feast-dev/feast-java-old
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·