feast-dev/feast

Returned feature vector when on demand feature views are specified output dependent features

Open

#1,999 opened on Nov 4, 2021

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Python (5,029 stars) (896 forks)batch import
Community Contribution Neededcriticalgood first issuekeep-openkind/bugpriority/p2

Description

When specifying on demand feature views at retrieval time (e.g. get_X_features), the output feature vectors include e.g. request data or dependent feature vectors, even if users did not specify said features.

Expected Behavior

Non-specified dependent feature values are not returned in output

Current Behavior

Non-specified dependent feature values are in output

Steps to reproduce

Specifications

  • Version:
  • Platform:
  • Subsystem:

Possible Solution

Contributor guide

Tech stack
python
Domain
datamachine learning
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of FeastUnderstanding of feature viewsPython programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the retrieval logic in Feast's Python SDK, particularly in the `get online features` or similar functions that assemble feature vectors when on demand feature views are specified. Look at how dependent features are included and ensure they are filtered out when not requested. Check for any existing work in progress from linked PRs or comments.