Is your feature request related to a problem? Please describe.
The process of integrating Feast with model serving frameworks like BentoML is error prone (e.g. around versioning)
Describe the solution you'd like
Some example integrations, using Feast object tags as a mechanism for passing information between systems:
Ex: metadata integration (bento model versions <> feature service versions)
Ex: code level assertions if you’re using feast[bento]
Several things would be nice:
[ ] write best practice documentation on both sides (Bento + Feast) (Sean, @Talador12 @adchia)
[ ] write a design doc on right integrations above
Describe alternatives you've considered
Stay as is. Users can manage their own naming conventions and ensure model versions in BentoML map well to feature services in Feast.
Additional context
Add any other context or screenshots about the feature request here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe. The process of integrating Feast with model serving frameworks like BentoML is error prone (e.g. around versioning)
Describe the solution you'd like Some example integrations, using Feast object tags as a mechanism for passing information between systems:
Several things would be nice:
Describe alternatives you've considered Stay as is. Users can manage their own naming conventions and ensure model versions in BentoML map well to feature services in Feast.
Additional context Add any other context or screenshots about the feature request here.