Support in memory SQLite online store
See original GitHub issueIs your feature request related to a problem? Please describe. When creating a SQLite online store your only option is to create it on the filesystem. As every access needs to hit the filesystem then this slows down the online store.
Describe the solution you’d like
I’d like an option :memory:
to use an in memory SQLite store instead. Eg in feature_store.yaml
:
online_store:
type: sqlite
path: :memory:
Currently if you do this feast
still tries to interpret this as a path
🙃
Describe alternatives you’ve considered
An alternative would be to change the key from path
however it’s common to use :memory:
as the path.
Additional context Add any other context or screenshots about the feature request here.
Issue Analytics
- State:
- Created a year ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
In-Memory Databases
An SQLite database is normally stored in a single ordinary disk file. However, in certain circumstances, the database might be stored in memory....
Read more >SQL Online Compiler - Next gen SQL Editor
SQL OnLine - Next gen SQL Editor: SQLite, MariaDB / MySQL, PostgreSQL, MS SQL Server. User-friendly interface for data science. No registration for...
Read more >In-memory databases - Microsoft.Data.Sqlite
In this article SQLite in-memory databases are databases stored entirely in memory, not on disk. Use the special data source filename :memory: ...
Read more >Save data using SQLite
Put information into a database · val db = dbHelper.writableDatabase // Create a new map of values, where column names are the keys...
Read more >What Is an In-Memory Database?
In-memory databases are purpose-built databases that rely primarily on memory for data storage, in contrast to databases that store data on disk or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I think what is actually ideally would be to have an in process cache (the in memory SQLite online store) for the feature server (when deploying
feast serve
). Then you can init the online store to live longer than a single request. This then serves as a cache for values in a more robust longer living database.As discussed in the feast dev weekly, we aren’t really sure what the requirements are here or whether this is an antipattern, so closing. Feel free to reopen