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
{{ message }}
Repository navigation
Commit 0a069ef
Browse filesBrowse the repository at this point in the historyBrowse files
feat(feast): switch registry from file to SQLite SQL backend
registry_type: sql with path sqlite:////tmp/registry.db gives proper
transactional semantics (atomic per-object writes, safe concurrent
materialization) with identical maintenance burden to the plain file
registry — no server, no operator, just a file on disk.
- feature_store.yaml: registry_type: file -> sql, sqlite:// path format
- feast-cr.yaml: note that operator CRD only supports local (file)
registry spec; PVC setup is identical for both
- README: update architecture table and note; reference upstream
deadlock bug feast-dev/feast#5565 fixed in 0.54.0 (PR #5588)
|**Registry**| Stores feature definitions (entities, feature views, sources). Written on `feast apply`, read at startup. | SQLite on PVC | SQL databases (PostgreSQL, etc.) for multi-replica or shared setups|
102
+
|**Registry**| Stores feature definitions (entities, feature views, sources). Written on `feast apply`, read at startup. | SQLite SQL on PVC (`registry_type: sql`) | Plain file (`registry_type: file`); PostgreSQL/MySQL for multi-replica |
93
103
|**Online store**| Holds the *latest* feature value per entity. Read on every inference request — latency critical. | Redis (your `Redis` CR) | SQLite on PVC (dev/test only; not multi-replica safe) |
94
104
|**Offline store**| Historical feature records for point-in-time joins during training. Batch workload, not on serving path. | Parquet/file on PVC | Dask (same parquet files, distributed compute — use only if data exceeds pod memory); cloud warehouses (BigQuery, Snowflake, Redshift) |
0 commit comments