We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Write updates (inserts/deletes) into the Feast online and offline stores.
This could potentially be implemented by reading the providers in the Feast config file and writing to them directly. e.g.
from ralf import Ralf, FeastConnector ralf = Ralf() connector = FeastConnector(config="feature_store.yaml") # read providers and connect
The text was updated successfully, but these errors were encountered:
Should the same table be allowed to have multiple connectors? e.g. one table should be stored in Feast and in Redis or something?
Sorry, something went wrong.
Should the same table be allowed to have multiple connectors?
This but it should be implemented in a layer above. Something like:
connector = MultiplexingConnect([FeastConnector(), RedisConnector()])
Why that approach over TableState(schema, List[Connector])? @simon-mo
TableState(schema, List[Connector])
Abstractions. Now table only cares about writing to a single connector and it's kept simple.
sarahwooders
simon-mo
narang-amit
No branches or pull requests
Write updates (inserts/deletes) into the Feast online and offline stores.
This could potentially be implemented by reading the providers in the Feast config file and writing to them directly. e.g.
The text was updated successfully, but these errors were encountered: