Title: 'feast apply' does not create online store tables in remote mode · Issue #6693 · feast-dev/feast · GitHub
Open Graph Title: 'feast apply' does not create online store tables in remote mode · Issue #6693 · feast-dev/feast
X Title: 'feast apply' does not create online store tables in remote mode · Issue #6693 · feast-dev/feast
Description: Expected Behavior With online_store.type: remote + registry.registry_type: remote, a client-side feast apply should create the corresponding feature view tables in the server-side online store, so that feast materialize can load data suc...
Open Graph Description: Expected Behavior With online_store.type: remote + registry.registry_type: remote, a client-side feast apply should create the corresponding feature view tables in the server-side online store, so ...
X Description: Expected Behavior With online_store.type: remote + registry.registry_type: remote, a client-side feast apply should create the corresponding feature view tables in the server-side online store, so ...
Opengraph URL: https://github.com/feast-dev/feast/issues/6693
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"'feast apply' does not create online store tables in remote mode","articleBody":"## Expected Behavior\n\nWith `online_store.type: remote` + `registry.registry_type: remote`, a client-side `feast apply` should create the corresponding feature view tables in the server-side online store, so that `feast materialize` can load data successfully — i.e. the schema setup done by `SqliteOnlineStore.update()` during a local `feast apply` should also take effect on the feature-server side when feature views are applied through the remote registry.\n\n## Current Behavior\n\n`feast apply` (remote) succeeds and registers the feature view, but **no table is created server-side**:\n\n- After `feast apply`, `online_store.db` does not exist (only `registry_sqlite.db` is present).\n- `feast materialize` reads offline data on the client, POSTs batches to the feature server's `/write-to-online-store`, and gets **HTTP 500**. The materialize command fails:\n\n```\nrequests.exceptions.RetryError: HTTPConnectionPool(host='localhost', port=6566): Max retries exceeded with url: /write-to-online-store (Caused by ResponseError('too many 500 error responses'))\n```\n\nFeature server log shows the root cause:\n\n```\nFile \".../feast/feature_store.py\", line 3126, in write_to_online_store\n provider.ingest_df(feature_view, df)\nFile \".../feast/infra/passthrough_provider.py\", line 197, in online_write_batch\n self.online_store.online_write_batch(config, table, data, progress)\nFile \".../feast/infra/online_stores/sqlite.py\", line 220, in online_write_batch\n conn.execute(\nsqlite3.OperationalError: no such table: test_project_driver_hourly_stats\n```\n\nAfter the failed materialize, `online_store.db` exists but is **0 bytes with zero tables**.\n\nRoot cause (in source):\n\n- `RemoteOnlineStore.update()` is a **no-op** (`pass`): `feast/infra/online_stores/remote.py` L706-715. `feast apply` relies on `OnlineStore.update()` to create tables, so remote apply never creates them on the server-side online store.\n- `feast serve` does **not** call `SqliteOnlineStore.update()` for newly-applied feature views, so the table is never created server-side either.\n- `SqliteOnlineStore.online_write_batch()` only `INSERT`s (no `CREATE TABLE`): `feast/infra/online_stores/sqlite.py` L152-239. Table creation happens only in `update()` (L291-315), which is never invoked in this flow.\n\nNet effect: the remote online store path is unusable for materialization unless the user manually runs `feast apply` locally on the feature-server repo, defeating the purpose of the remote architecture.\n\n## Steps to reproduce\n\nSetup: a **server repo** (`test_project/feature_repo`) hosting registry + online store, and a **client repo** (`test_demo`) using remote registry + remote online store.\n\n1. Server repo `test_project/feature_repo/feature_store.yaml`:\n\n```yaml\nproject: test_project\nregistry:\n registry_type: sql\n path: sqlite:///data/registry_sqlite.db\nprovider: local\nonline_store:\n type: sqlite\n path: data/online_store.db\nentity_key_serialization_version: 3\nauth:\n type: no_auth\n```\n\n2. Client repo `test_demo/feature_store.yaml` (remote registry + remote online store):\n\n```yaml\nproject: test_project\nregistry:\n registry_type: remote\n path: localhost:6570 # feast serve_registry (gRPC)\nprovider: local\nonline_store:\n type: remote\n path: http://localhost:6566 # feast serve (HTTP feature server)\nentity_key_serialization_version: 3\nauth:\n type: no_auth\n```\n\n3. Client repo `test_demo/feature_definitions.py` (a single simple FeatureView):\n\n```python\nfrom datetime import timedelta\nfrom feast import Entity, FeatureView, Field, FileSource, Project\nfrom feast.types import Float32, Int64\n\nproject = Project(name=\"test_project\", description=\"A project for driver statistics\")\ndriver = Entity(name=\"driver\", join_keys=[\"driver_id\"])\n\ndriver_stats_source = FileSource(\n name=\"driver_hourly_stats_source\",\n path=\"data/driver_stats.parquet\",\n timestamp_field=\"event_timestamp\",\n created_timestamp_column=\"created\",\n)\n\ndriver_stats_fv = FeatureView(\n name=\"driver_hourly_stats\",\n entities=[driver],\n ttl=timedelta(days=1),\n schema=[\n Field(name=\"conv_rate\", dtype=Float32),\n Field(name=\"avg_daily_trips\", dtype=Int64),\n ],\n online=True,\n source=driver_stats_source,\n version=\"latest\",\n)\n```\n\n4. Start the servers from the server repo:\n\n```bash\ncd test_project/feature_repo\nfeast serve_registry --port 6570 # gRPC registry server\nfeast serve --port 6566 # HTTP feature server (separate shell)\n```\n\n5. From the client repo, apply (remote):\n\n```bash\ncd test_demo\nfeast apply\n# Applying changes for project test_project\n# Deploying infrastructure for driver_hourly_stats\n```\n\n6. Inspect the server-side online store — `online_store.db` does **not** exist (only `registry_sqlite.db`):\n\n```bash\nls test_project/feature_repo/data\n# registry_sqlite.db (online_store.db is absent)\n```\n\n7. From the client repo, materialize (remote):\n\n```bash\ncd test_demo\nfeast materialize 2021-04-12T00:00:00 2026-08-02T00:00:00\n```\n\n8. Observe the failure: client fails with `too many 500 error responses` against `/write-to-online-store`; feature server logs `sqlite3.OperationalError: no such table: test_project_driver_hourly_stats`; `online_store.db` is left as a 0-byte file with no tables.\n\n### Specifications\n\n- Version: Feast SDK 0.64.0 (Python 3.12.10)\n- Platform: Windows 11 (10.0.26200), AMD64 — relevant code is platform-independent, expected to reproduce on Linux/macOS too\n- Subsystem: `infra/online_stores/remote` (RemoteOnlineStore), `infra/online_stores/sqlite` (SqliteOnlineStore), feature server (`feast serve` / `write_to_online_store`)","author":{"url":"https://github.com/yuan1j","@type":"Person","name":"yuan1j"},"datePublished":"2026-08-01T07:58:23Z","url":"https://github.com/feast-dev/feast/issues/6693"}
| 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:a3e31df6-c01d-0067-b285-00146fc187c3 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B102:281DDB:FAEEA3:15B6BB7:6AFEA264 |
| html-safe-nonce | 4fa402b6ada098ebb214990d406ad775e750b062f329c072bf6732f05428f7f1 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMTAyOjI4MUREQjpGQUVFQTM6MTVCNkJCNzo2QUZFQTI2NCIsInZpc2l0b3JfaWQiOiI0OTM3NDAxNjk0MTEyNjIxMTU2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | f2d9efe2d3df6fa3f32085accc81163a3bbaf9cfb8b1dfbda195a0dcc62b4b20 |
| hovercard-subject-tag | issue:5036042336 |
| 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/6693/issue_layout |
| twitter:image | https://opengraph.githubassets.com/835316764b48841db81e68a171c293dab48c20d3c80fb05d5aeb9d28978fec0d/feast-dev/feast/issues/6693 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/835316764b48841db81e68a171c293dab48c20d3c80fb05d5aeb9d28978fec0d/feast-dev/feast/issues/6693 |
| og:image:alt | Expected Behavior With online_store.type: remote + registry.registry_type: remote, a client-side feast apply should create the corresponding feature view tables in the server-side online store, so ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | yuan1j |
| hostname | github.com |
| expected-hostname | github.com |
| None | 95b2753c978240785d6cca00783c00a371b2d7d9879bb32e305170a1b19bd28e |
| 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 | 3f25273206cd841171bca0002261ae4c9757d934 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width