Title: Remote registry client fails with ModuleNotFoundError: No module named 'grpc' unless the unrelated [grpcio] extra is installed · Issue #6666 · feast-dev/feast · GitHub
Open Graph Title: Remote registry client fails with ModuleNotFoundError: No module named 'grpc' unless the unrelated [grpcio] extra is installed · Issue #6666 · feast-dev/feast
X Title: Remote registry client fails with ModuleNotFoundError: No module named 'grpc' unless the unrelated [grpcio] extra is installed · Issue #6666 · feast-dev/feast
Description: Expected Behavior Installing Feast with any extra that supports a remote registry, and configuring registry_type: remote, should work — grpcio should be present because the remote registry client cannot run without it. Current Behavior s...
Open Graph Description: Expected Behavior Installing Feast with any extra that supports a remote registry, and configuring registry_type: remote, should work — grpcio should be present because the remote registry client c...
X Description: Expected Behavior Installing Feast with any extra that supports a remote registry, and configuring registry_type: remote, should work — grpcio should be present because the remote registry client c...
Opengraph URL: https://github.com/feast-dev/feast/issues/6666
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Remote registry client fails with ModuleNotFoundError: No module named 'grpc' unless the unrelated [grpcio] extra is installed","articleBody":"## Expected Behavior\n\nInstalling Feast with any extra that supports a remote registry, and configuring\n`registry_type: remote`, should work — `grpcio` should be present because the\nremote registry client cannot run without it.\n\n## Current Behavior\n\n`sdk/python/feast/infra/registry/remote.py` does an unconditional module-level\n`import grpc`. `grpcio` is declared only in the `grpcio` optional-dependency\ngroup in `pyproject.toml`, and no other extra depends on it. So an install such\nas `pip install feast[redis]` or `feast[postgres]` resolves cleanly and then\nfails at runtime as soon as the remote registry is constructed:\n\n```\nModuleNotFoundError: No module named 'grpc'\n```\n\nThe `grpcio` extra reads as being about serving gRPC (it also pulls\n`grpcio-reflection` and `grpcio-health-checking`, which a client does not need),\nso there is nothing to suggest a registry *client* requires it. The failure\nsurfaces only at runtime, in a code path unrelated to anything the user\ninstalled.\n\n## Steps to reproduce\n\n1. `pip install \"feast[postgres]==0.64.0\"` in a clean virtualenv.\n\n2. `feature_store.yaml`:\n\n ```yaml\n project: demo\n registry:\n registry_type: remote\n path: registry.example:80\n provider: local\n ```\n\n3. ```python\n from feast import FeatureStore\n FeatureStore(repo_path=\".\").list_feature_views()\n ```\n\n4. Fails with `ModuleNotFoundError: No module named 'grpc'`.\n\n### Specifications\n\n- Version: 0.64.0; unchanged on 0.65.0 (latest release) and `master`. On 0.65.0\n the `redis` extra pulls only `redis` and `hiredis`, and `grpcio` remains\n declared solely in the `grpcio` extra.\n- Platform: Linux, Python 3.12\n- Subsystem: packaging / registry — `feast.infra.registry.remote`\n\n## Possible Solution\n\nThe dependency has to become reachable — the only question is how.\n\n1. **Move `grpcio` into the core dependencies.** The remote registry is a\n first-class registry type, and `grpcio` ships a wheel on every supported\n platform. This is the only option that fixes an existing\n `pip install feast[postgres]` without the user changing anything.\n2. **Add a client-only extra** (for example `remote`) that pulls just `grpcio`,\n and document it as required for `registry_type: remote`. Users still have to\n edit their install line, but there is then a correct one to point them at. The\n existing `grpcio` extra is a poor substitute: it also pulls\n `grpcio-reflection` and `grpcio-health-checking`, which a registry *client*\n does not need, and its name reads as being about serving gRPC.\n\nA lazy import that raises a clear Feast error naming the extra would be an\nimprovement on the bare `ModuleNotFoundError`, but it is worth being explicit\nthat it does **not** fix this: the remote registry still cannot run, the call\nstill fails, and the user is still stuck until the dependency is installed. Good\ndiagnostics are worth having alongside (1) or (2), not instead of them.\n\nOur workaround is to add `grpcio` to the dependency set of the module that builds\nthe store, which is invisible to anyone reading `pyproject.toml` for what a\nremote registry needs.\n","author":{"url":"https://github.com/BigyaPradhan","@type":"Person","name":"BigyaPradhan"},"datePublished":"2026-07-30T09:06:07Z","url":"https://github.com/feast-dev/feast/issues/6666"}
| 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:b9fe5f60-9c58-855b-1094-0dfb00e2e74f |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E7C8:A7C4D:F0DD1C:1491306:6AFE981E |
| html-safe-nonce | b9b8b6d580ff3d85808cad89d776c087f84c37f513b3d349a5f6e24cf7d1a3b5 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFN0M4OkE3QzREOkYwREQxQzoxNDkxMzA2OjZBRkU5ODFFIiwidmlzaXRvcl9pZCI6IjE0NTE3NDc4Mjg4NjU4NjU3NTgiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 4b355242480134202b41a69d7279a3414514268b96ec5d9a0e8c44ddc405ddc8 |
| hovercard-subject-tag | issue:5018077886 |
| 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/6666/issue_layout |
| twitter:image | https://opengraph.githubassets.com/1faaeb76fdc939a96f8c9cec1a76301474053a04f0e6a904dbcec837ea6aab99/feast-dev/feast/issues/6666 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/1faaeb76fdc939a96f8c9cec1a76301474053a04f0e6a904dbcec837ea6aab99/feast-dev/feast/issues/6666 |
| og:image:alt | Expected Behavior Installing Feast with any extra that supports a remote registry, and configuring registry_type: remote, should work — grpcio should be present because the remote registry client c... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | BigyaPradhan |
| 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 | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width