René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Historical retrieval without an entity dataframe","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nThe current Feast `get_historical_features()` method requires that users provide an entity dataframe as follows\r\n\r\n```python\r\ntraining_df = store.get_historical_features(\r\n    entity_df=entity_df, \r\n    feature_refs = [\r\n        'drivers_activity:trips_today'\r\n        'drivers_profile:rating'\r\n    ],\r\n)\r\n```\r\nHowever, many users would like the feature store to provide entities to them for training, instead of having to query or provide entities as part of the entity dataframe.\r\n\r\n**Describe the solution you'd like**\r\nAllow users to specify an existing feature view from which an entity dataframe will be queried.\r\n\r\n```python\r\ntraining_df = store.get_historical_features(\r\n    entity_df=\"drivers_activity\", \r\n    feature_refs = [\r\n        'drivers_activity:trips_today'\r\n        'drivers_profile:rating'\r\n    ],\r\n)\r\n```\r\n\r\nWith the addition of time range filtering.\r\n\r\n```python\r\ntraining_df = store.get_historical_features(\r\n    entity_df=\"drivers_activity\", \r\n    feature_refs = [\r\n        'drivers_activity:trips_today'\r\n        'drivers_profile:rating'\r\n    ],\r\n    from_date=(today - timedelta(days = 7)),\r\n    to_date=datetime.now(),\r\n)\r\n```\r\n","author":{"url":"https://github.com/woop","@type":"Person","name":"woop"},"datePublished":"2021-06-01T19:31:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":22},"url":"https://github.com/1611/feast/issues/1611"}