feat: Add HybridOfflineStore for supporting multiple offline store backends#5542
feat: Add HybridOfflineStore for supporting multiple offline store backends#5542PrasannaKumarARDS wants to merge 3 commits intofeast-dev:hybrid-offline-storefrom
Conversation
- Implements HybridOnlineStore, enabling routing of online feature operations to different backends based on a configurable tag (e.g., tribe, team, or project) on the FeatureView. - Adds support for specifying the routing tag name via the 'routing_tag' field in the online_store config, allowing flexible backend selection. - Supports multi-tenancy and flexible data management by allowing multiple online store backends in a single Feast deployment. - added documentation - fixed linter raised issues Signed-off-by: r0b0fyi <renukaprasannakumar.badugu@walmart.com>
- Implements HybridOnlineStore, enabling routing of online feature operations to different backends based on a configurable tag (e.g., tribe, team, or project) on the FeatureView. - Adds support for specifying the routing tag name via the 'routing_tag' field in the online_store config, allowing flexible backend selection. - Supports multi-tenancy and flexible data management by allowing multiple online store backends in a single Feast deployment. - added documentation - fixed linter raised issues Signed-off-by: r0b0fyi <renukaprasannakumar.badugu@walmart.com>
The HybridOfflineStore allows routing operations to different offline store implementations based on data source type. This enables a single Feast deployment to work with multiple offline storage backends simultaneously, improving flexibility for organizations with heterogeneous data infrastructure. Key features: - Configure multiple offline stores in a single Feast deployment - Automatic routing of operations to the appropriate offline store - Support for all existing offline store operations - Transparent to feature views and other Feast components Signed-off-by: r0b0fyi <renukaprasannakumar.badugu@walmart.com>
|
Really appreciate your contribution. I made the first version of the hybrid store and already in the codebase now. Do you mind taking a look see if there is something missing and you want to optimize? |
|
@PrasannaKumarARDS any update on this? |
|
Apologies for missing this earlier. I will review the version/implementation available at the earliest opportunity and provide feedback or recommendations for any potential improvements. Thank you for your patience, and I appreciate you highlighting this. |
|
I believe |
|
@PrasannaKumarARDS any update on this? Want to see if we should aim to get it in the next release |
What this PR does / why we need it:
This PR adds a new HybridOfflineStore implementation that can route operations to different offline stores based on data source type. This enables organizations with heterogeneous data infrastructure to use a single Feast deployment while storing features in multiple different storage systems.
Key features:
Which issue(s) this PR fixes:
Fixes #5541
Misc
This implementation follows the existing patterns in Feast's offline store design. It introduces a new configuration type
HybridOfflineStoreConfigthat contains a list of offline store configurations.Testing: