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
ROX-18155: pg generic store: DeleteByQuery #6774
ROX-18155: pg generic store: DeleteByQuery #6774
Conversation
Images are ready for the commit at fb141f1. To use with deploy scripts, first |
42ab190
to
91f09f5
Compare
45ea17e
to
6766f93
Compare
91f09f5
to
36679e0
Compare
6766f93
to
2e100d1
Compare
36679e0
to
efaad61
Compare
2e100d1
to
ddfc8a1
Compare
efaad61
to
043cf9f
Compare
ddfc8a1
to
3f6dff3
Compare
|
||
// DeleteByQuery removes the objects from the store based on the passed query. | ||
func (s *GenericStore[T, PT]) DeleteByQuery(ctx context.Context, query *v1.Query) error { | ||
defer s.setPostgresOperationDurationTime(time.Now(), ops.Remove) |
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.
While not directly linked to the change at hand, it might be good to differentiate Delete
from DeleteByQuery
in the stat histograms. If the filter of DeleteByQuery
is complex enough, this would introduce false outliers in the distribution.
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.
Ideally we should track time and length of the query together so we can see correlation. Anyway I think it might be hard after this simplification: #6775 (comment)
043cf9f
to
d8a82a8
Compare
3f6dff3
to
f8c2863
Compare
d8a82a8
to
a55c307
Compare
f8c2863
to
8eda922
Compare
a55c307
to
2cffae6
Compare
c9fa819
to
182c002
Compare
2cffae6
to
e17c60a
Compare
182c002
to
67da9dd
Compare
e17c60a
to
569f2ba
Compare
Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready. |
67da9dd
to
fb141f1
Compare
@janisz: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist
If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.