-
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
Don't allow FeatureStore.apply with commit=False #2047
Don't allow FeatureStore.apply with commit=False #2047
Conversation
The apply method will call update_infra for the provider without offering a dry run, so invoking it without committing should not be an option. It would make all the infra updates but not update the registry causing them to be out of sync. Added commit=False to apply_feature_service and apply_feature_table in the apply method. Today when calling apply, the update_infra might fail but then we have already updated the registry causing everything to be out of sync. Signed-off-by: Gunnar Sv Sigurbjörnsson <gunnar.sigurbjornsson@gmail.com>
Hi @nossrannug. Thanks for your PR. I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thanks for identifying the bug and the fix @nossrannug! |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, nossrannug The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #2047 +/- ##
===========================================
+ Coverage 60.01% 83.41% +23.40%
===========================================
Files 103 100 -3
Lines 8523 8026 -497
===========================================
+ Hits 5115 6695 +1580
+ Misses 3408 1331 -2077
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/kind bug |
What this PR does / why we need it:
The
FeatureStore.apply
method will callupdate_infra
for the provider withoutoffering a dry run, so invoking it without committing should not be
an option. It would make all the infra updates but not update the
registry causing them to be out of sync.
Added
commit=False
toapply_feature_service
andapply_feature_table
in theapply
method.Which issue(s) this PR fixes:
When calling
feast apply
and adding a feature table or feature servicethe registry will get updated even if the update_infra call fails.
This PR makes the only registry commit happen after the call to update_infra
has completed successfully.
Does this PR introduce a user-facing change?: