Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestion from @franciscojavierarceo
  • Loading branch information
franciscojavierarceo authored Apr 1, 2026
commit 019a41545c977de6e82f78d5b08fa73528119b98
2 changes: 1 addition & 1 deletion infra/website/docs/blog/feature-view-versioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ These tradeoffs are real and we're still refining the model based on community e

This is an experimental feature and there are known gaps:

- **Online store support** — Version-qualified reads (`@v<N>`) are **SQLite-only** today. We plan to add Redis, DynamoDB, Bigtable, Postgres, and others based on community demand. If you need a specific store, [open a GitHub issue](https://github.com/feast-dev/feast/issues/new) and let us know.
- **Online store support** — Version-qualified reads (`@v<N>`) are **SQLite-only** today. We plan to add Redis, DynamoDB, Bigtable, Postgres, and others based on community demand. If you need a specific store, [comment or upvote on the appropriate the child GitHub issue of the main GitHub issue](https://github.com/feast-dev/feast/issues/2728) and let us know.
- **Offline store versioning** — Versioned historical retrieval is not yet supported.
- **Version deletion** — There is no mechanism today to prune old versions from the registry.
- **Feature services** — Feature services always resolve to the active (promoted) version. `--no-promote` versions are not accessible through feature services until promoted.
Expand Down
Loading