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

In Memory Registry #4078

Open
franciscojavierarceo opened this issue Apr 5, 2024 · 1 comment
Open

In Memory Registry #4078

franciscojavierarceo opened this issue Apr 5, 2024 · 1 comment
Assignees
Labels
kind/feature New feature or request

Comments

@franciscojavierarceo
Copy link
Member

Is your feature request related to a problem? Please describe.
We would benefit from implementing an in memory registry so that if Feast users choose to rely on a full deployment to enable new feature views, the can use it.

Describe the solution you'd like
Registry purely based on code and no database lookup.

Describe alternatives you've considered
N/A

Additional context
N/A

@franciscojavierarceo franciscojavierarceo added the kind/feature New feature or request label Apr 5, 2024
@franciscojavierarceo franciscojavierarceo self-assigned this Apr 5, 2024
@tokoko
Copy link
Collaborator

tokoko commented Apr 6, 2024

Can you elaborate on the use case here? Is it only supposed to be used for local development? Also, how would this differ from using for example a file-based registry that has caching enabled (without ttl)? Isn't that essentially the same thing already?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants