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
feat: Make feature view versioning opt-in via registry config
Versioning was always active on every `feast apply`. This adds an
`enable_feature_view_versioning` boolean (default False) to
RegistryConfig so version history, version pins, and version-qualified
refs are only available when explicitly enabled. Existing behaviour is
fully preserved when the flag is set to true.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Version-qualified reads (`@v<N>`) are currently supported only on the SQLite online store. See the [feature view versioning docs](feature-view.md#version-qualified-feature-references) for details.
103
+
Version-qualified reads (`@v<N>`) require `enable_feature_view_versioning: true` in your registry config and are currently supported only on the SQLite online store. See the [feature view versioning docs](feature-view.md#version-qualified-feature-references) for details.
104
104
{% endhint %}
105
105
106
106
It is possible to retrieve features from multiple feature views with a single request, and Feast is able to join features from multiple tables in order to build a training dataset. However, it is not possible to reference (or retrieve) features from multiple projects at the same time.
Copy file name to clipboardExpand all lines: docs/getting-started/concepts/feature-view.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,9 +164,21 @@ Each field can have additional metadata associated with it, specified as key-val
164
164
165
165
Feature views support automatic version tracking. Every time `feast apply` detects a change to a feature view, a version snapshot is saved to the registry's version history. This enables auditing what changed, reverting to a prior definition, or pinning serving to a known-good version.
166
166
167
+
{% hint style="warning" %}
168
+
Versioning is **opt-in** and disabled by default. To enable it, add `enable_feature_view_versioning: true` to your registry config in `feature_store.yaml`:
169
+
170
+
```yaml
171
+
registry:
172
+
path: data/registry.db
173
+
enable_feature_view_versioning: true
174
+
```
175
+
176
+
When disabled, `feast apply` works normally but does not create version history. Version-qualified refs (e.g., `fv@v2:feature`) and version pinning (e.g., `version="v0"`) will raise errors.
177
+
{% endhint %}
178
+
167
179
### How it works
168
180
169
-
Version tracking is fully automatic. You don't need to set any version parameter — just use `feast apply` as usual:
181
+
Once versioning is enabled, version tracking is fully automatic. You don't need to set any version parameter — just use `feast apply` as usual:
170
182
171
183
1. **First apply** — Your feature view definition is saved as **v0**.
172
184
2. **Change something and re-apply** — Feast detects the change, saves the old definition as a snapshot, and saves the new one as **v1**. The version number auto-increments on each real change.
0 commit comments