fix: Add remote registry client extra - #6697
Conversation
|
The implementation is ready and the branch is mergeable. Per the repository contribution guide, could a maintainer add the required |
ca3823a to
9e9ee68
Compare
franciscojavierarceo
left a comment
There was a problem hiding this comment.
The focused extra cleanly separates the client-only grpcio dependency and documents the installation path without changing the existing server extra. I found no blocking issue in the remote diff.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6697 +/- ##
=======================================
Coverage 46.80% 46.81%
=======================================
Files 415 415
Lines 50395 50396 +1
Branches 7214 7214
=======================================
+ Hits 23587 23591 +4
+ Misses 25155 25154 -1
+ Partials 1653 1651 -2
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
6bb1eb7 to
47f74b3
Compare
47f74b3 to
43c0ea3
Compare
Signed-off-by: buduoqiu <shenyaodong@hhu.edu.cn>
Signed-off-by: buduoqiu <shenyaodong@hhu.edu.cn>
43c0ea3 to
e3b331b
Compare
What this PR does
Fixes #6666.
RemoteRegistryimportsgrpcunconditionally, butgrpciowas only available through the unrelated server-orientedgrpcioextra. Users installing a normal provider extra could therefore configureregistry_type: remoteand receiveModuleNotFoundErrorat runtime.This adds a focused
remoteoptional dependency containing onlygrpcioand documentspip install "feast[remote]"next to the remote registry configuration. The existinggrpcioextra remains unchanged for registry/feature-server deployments that need reflection and health-checking packages.Validation
pyproject.tomlanddocs/reference/registries/remote.md.Release notes
NONE