feast-dev/feast

Historical retrieval without an entity dataframe

Open

#1,611 创建于 2021年6月1日

在 GitHub 查看
 (22 评论) (44 反应) (1 负责人)Python (896 fork)batch import
Community Contribution Neededgood first issuekeep-openkind/featurekind/projectpriority/p1

仓库指标

Star
 (5,029 star)
PR 合并指标
 (平均合并 9天 1小时) (30 天内合并 59 个 PR)

描述

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

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.

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.

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(),
)

贡献者指南