feast plan
and `feast apply will throw errors if it sees this kind of behavior.get_historical_features
without providing an entity dataframe?get_historical_features
and at online serving time when you call `get_online_features.feature_store.yaml
primarily sets default offline / online stores and configures where the remote registry file can live (Using the AWS provider also allows for deployment to AWS Lambda). You can override the offline and online stores to be in different clouds if you wish.s3_endpoint_override
in a FileSource
data source. This endpoint is more suitable for quick proof of concepts that won't necessarily scale for production use cases.