-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: Do not pass undeclared feature view columns to ODFV UDFs #6527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ntkathole
merged 2 commits into
feast-dev:master
from
Vedant-Agarwal:fix/odfv-source-isolation
Jul 30, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FeatureViewProjectioncan carry aname_aliasor version tag, but these comparisons and column names use.name. For an ODFV sourced from an aliased projection, won’t the alias-qualified input be classified as undeclared whilealias__featurealso escapes the second filter? Should these useprojection.name_to_use()instead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Sanjays2402 — fair question, so I verified it against this branch (checked out this PR's head) rather than guess.
With an ODFV sourced from an aliased projection:
the columns feeding the transform come through as
['driver_stats__conv_rate', 'conv_rate']—.name-qualified, not alias-qualified. That's consistent with how source refs are built throughouton_demand_feature_view.py(f"{source_fv_projection.name}__{feature.name}", e.g. the loops around lines 987/1055/1151/1261). So.namematches the real column names here; switching toname_to_use()would buildaliased_stats__conv_rate, which isn't present, and would drop the declared feature.On
version_tag: it's only set viafrom_proto(there's no user-facing setter), and the retrieval path keys source columns by.nameregardless — so even a versioned projection's column is stilldriver_stats__conv_rate.I'll add a test with an aliased source to lock this behavior in. If you know a path (offline retrieval?) where the input comes through alias-qualified, point me at it and I'll handle that too — I exercised online retrieval here.