Title: Allow serving online features while a FeatureView is `MATERIALIZING` (config to relax the lifecycle serving gate) · Issue #6780 · feast-dev/feast · GitHub
Open Graph Title: Allow serving online features while a FeatureView is `MATERIALIZING` (config to relax the lifecycle serving gate) · Issue #6780 · feast-dev/feast
X Title: Allow serving online features while a FeatureView is `MATERIALIZING` (config to relax the lifecycle serving gate) · Issue #6780 · feast-dev/feast
Description: Summary Since v0.64.0, get_online_features refuses to serve any FeatureView whose lifecycle state is not AVAILABLE_ONLINE/STATE_UNSPECIFIED. Because store.materialize() transitions a FV to MATERIALIZING in the (shared) registry for the d...
Open Graph Description: Summary Since v0.64.0, get_online_features refuses to serve any FeatureView whose lifecycle state is not AVAILABLE_ONLINE/STATE_UNSPECIFIED. Because store.materialize() transitions a FV to MATERIAL...
X Description: Summary Since v0.64.0, get_online_features refuses to serve any FeatureView whose lifecycle state is not AVAILABLE_ONLINE/STATE_UNSPECIFIED. Because store.materialize() transitions a FV to MATERIAL...
Opengraph URL: https://github.com/feast-dev/feast/issues/6780
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow serving online features while a FeatureView is `MATERIALIZING` (config to relax the lifecycle serving gate)","articleBody":"## Summary\nSince **v0.64.0**, `get_online_features` refuses to serve any FeatureView whose lifecycle state is\nnot `AVAILABLE_ONLINE`/`STATE_UNSPECIFIED`. Because `store.materialize()` transitions a FV to\n`MATERIALIZING` in the (shared) registry for the duration of its run, **online serving fails for that\nFV while it is being materialized**. For the canonical setup — a long-running `feast serve` plus a\nperiodic (incremental) materialization job sharing one registry — this turns routine materialization\ninto recurring online-serving outages. Requesting a config option to keep serving the last-materialized\nvalues during `MATERIALIZING`.\n\n## Current behavior\n`sdk/python/feast/utils.py` (`_get_online_features`) enforces an unconditional gate:\n\n```python\nraise ValueError(\n f\"Feature view '{name}' is in state '{fv.state.name}' \"\n f\"and cannot serve features. Only AVAILABLE_ONLINE feature views can serve.\"\n)\n```\n\n`FeatureStore.materialize()` sets the FV to `MATERIALIZING` and commits it to the registry before\nwriting (`feature_view.state = FeatureViewState.MATERIALIZING; self.registry.apply_feature_view(..., commit=True)`).\nA separate feature server reading the same registry (subject to `cache_ttl_seconds`) then observes\n`MATERIALIZING` and rejects requests. Since a `get_online_features` call spans all requested FVs, a\n**single** materializing FV fails the **entire** request (including any feature service that references it).\n\n## Steps to reproduce\n1. `feast apply`, then materialize once so the FV is `AVAILABLE_ONLINE`.\n2. Start `feast serve`; confirm `/get-online-features` works.\n3. Run `feast materialize` for that FV (or set its state to `MATERIALIZING`).\n4. Call `/get-online-features` for the same FV during the run →\n `ValueError: Feature view '\u003cname>' is in state 'MATERIALIZING' and cannot serve features.`\n\n## Impact\n- Continuous online serving + periodic incremental materialization is the standard online pattern;\n with one shared registry the serving tier unavoidably observes `MATERIALIZING`.\n- Materialization is exactly when the *previous* values are still valid and should keep being served;\n instead reads hard-fail.\n- Blast radius is the whole request / feature service, not just the one FV.\n\n## When it was introduced\nThe gate was added in **PR #6401** (“Add enabled/disabled toggle for feature views”), first released in\n**v0.64.0**, and is present unchanged in **v0.65.0**, **v0.66.0**, and `master`. It is unconditional —\nthere is no config to opt out. Versions ≤ v0.63.x do not have it.\n\n## Proposed solution\nAdd a config flag (e.g. under `online_store` or top-level in `feature_store.yaml`) such as:\n\n```yaml\nserve_during_materialization: true # default false to preserve current behavior\n```\n\nWhen enabled, `_get_online_features` treats `MATERIALIZING` as servable (serves the last-materialized\nvalues) instead of raising. `GENERATED` / never-materialized FVs can still be gated. Alternatively,\nscope the gate so `MATERIALIZING` is always servable (only truly-unavailable states are rejected),\nsince a FV that is re-materializing already has prior data online.\n\n## Environment\n- Feast: 0.65.0 (also confirmed in 0.64.0, 0.66.0, master)\n- Online store: Redis · Offline store: Athena · Registry: file (S3), shared between `feast serve`\n and a scheduled `feast materialize`\n","author":{"url":"https://github.com/alan-gauthier-jt","@type":"Person","name":"alan-gauthier-jt"},"datePublished":"2026-08-25T10:08:18Z","url":"https://github.com/feast-dev/feast/issues/6780"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:c54c5d14-02ee-11e3-153c-ca351acd1a54 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C2C6:3C86C1:E986DA:132F644:6AFE951E |
| html-safe-nonce | e35be7872863c07d658c0554a3a6847e8c31ac0f0630a3b074b4db5ec3ede3be |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDMkM2OjNDODZDMTpFOTg2REE6MTMyRjY0NDo2QUZFOTUxRSIsInZpc2l0b3JfaWQiOiI4MDMxMDIyNzc3MjE1MzkxMDA2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | ddae882060a43d53cadac58d7e0f9e7eaf0f3eef1562e3d426133afebd295105 |
| hovercard-subject-tag | issue:5244641065 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/6780/issue_layout |
| twitter:image | https://opengraph.githubassets.com/a8057b55297e8c8bdabc93e202bb3c9c0d6cfb31ebaa15a53e4fa56b0fbb80a1/feast-dev/feast/issues/6780 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/a8057b55297e8c8bdabc93e202bb3c9c0d6cfb31ebaa15a53e4fa56b0fbb80a1/feast-dev/feast/issues/6780 |
| og:image:alt | Summary Since v0.64.0, get_online_features refuses to serve any FeatureView whose lifecycle state is not AVAILABLE_ONLINE/STATE_UNSPECIFIED. Because store.materialize() transitions a FV to MATERIAL... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | alan-gauthier-jt |
| hostname | github.com |
| expected-hostname | github.com |
| None | b3c0f155eafc27e60db6e254d1ffff0e072e9ab3b4018a5ee518797c19d89f86 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a10310af51a1bfffbedc4fd81cb582acf0cb0ff |
| ui-target | canary-1 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width