feast-dev / feast-dev/feast

Historical retrieval without an entity dataframe

Open
#1,611 22 comments 44 reactions 1 assignee Claimed by @jyejare View on GitHub
Community Contribution Needed good first issue keep-open kind/feature kind/project priority/p1
Dominant language
Python
Stars
7.3k
Forks
1.4k
Avg merge
1d 21h
Merged PRs (30d)
15

Description

**Is your feature request related to a problem? Please describe.**
The current Feast `get_historical_features()` method requires that users provide an entity dataframe as follows

```python
training_df = store.get_historical_features(
entity_df=entity_df,
feature_refs = [
'drivers_activity:trips_today'
'drivers_profile:rating'
],
)
```
However, 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.

**Describe the solution you'd like**
Allow users to specify an existing feature view from which an entity dataframe will be queried.

```python
training_df = store.get_historical_features(
entity_df="drivers_activity",
feature_refs = [
'drivers_activity:trips_today'
'drivers_profile:rating'
],
)
```

With the addition of time range filtering.

```python
training_df = store.get_historical_features(
entity_df="drivers_activity",
feature_refs = [
'drivers_activity:trips_today'
'drivers_profile:rating'
],
from_date=(today - timedelta(days = 7)),
to_date=datetime.now(),
)
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.