-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Deprecate the input parameter for FeatureViews #1765
Conversation
Signed-off-by: Felix Wang <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: felixwang9817 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #1765 +/- ##
===========================================
- Coverage 84.69% 64.21% -20.48%
===========================================
Files 85 82 -3
Lines 6297 6218 -79
===========================================
- Hits 5333 3993 -1340
- Misses 964 2225 +1261
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@felixwang9817 let's hold this for now. Pending a decision on OD transformations. |
/hold |
A quick followup here. We decided that ODFVs need to be able to take in other feature views as input for some important use cases, so input might need to stay |
@adchia we'll probably have a different class/proto for ODFVs though. Although I think it's still smart to have this PR stay held. |
Is this PR still relevant? |
@woop I think this change might still be useful? ODFVs have an |
Signed-off-by: Felix Wang [email protected]
What this PR does / why we need it: FeatureViews have always required a batch data source as input; this argument is currently named input. This PR removes input as an argument and makes batch_source required. Since this is a breaking change, it was preceded by a deprecation warning in #1729, which was part of the 0.12 release.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: