-
Notifications
You must be signed in to change notification settings - Fork 998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor stores #110
Refactor stores #110
Conversation
This PR includes changes from PR #89. As I expect that to be finished first. So don't review this too closely yet. But if you could take a look at the proposed naming and directory structure of the storage classes. Eg, I'm thinking:
And for a new "bar" serving store type, we'd have
The factories implement FeatureStoreFactory. [An inconsistency I'm bothered by is that in I think the factories should be able to validate storage specs, and create clients for accessing the serving stores (future work). Then the goal will be to make this it's own module and (without the beam dependencies)
|
Had a cursory look, and it looks great so far @tims! It would be nice to be able to share the storage modules across feast for sure |
90dfeda
to
df908fa
Compare
/cancel hold |
rebased (effectively) to master, @zhilingc @pradithya can you re-review? |
/hold cancel |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zhilingc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
any suggestions? |
/lgtm |
This is for #109
/hold