-
Notifications
You must be signed in to change notification settings - Fork 188
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
Filter getRequestHistory queries by createdAt times #2117
Conversation
@@ -253,5 +241,10 @@ void setDeployJson( | |||
@Bind("json") @Json SingularityDeployHistory deployHistory | |||
); | |||
|
|||
@Override | |||
default String getRequestHistoryBaseQuery() { |
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.
If this is just a constant let's declare it as a string on the class, not as a method, same for the mysql jdbi version
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.
The user column is named user
in the mysql version, and f_user
in the postgres version. That's why I didn't declare it as a constant.
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.
ah, totally read over that difference. It can still just be a String REQUEST_HISTORY_BASE_QUERY = "...";
on each class though, vs a method
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.
sry, read that again, ignore me...
Just the one comment on the static string vs method. Only other thing is to confirm that the history paging in the UI still seems to work as intended once deployed on staging 👍 , will give the ⛵ once you've tested there |
Tested on |
🚢 |
Instead of looping through the entire request history for some
requestId
to find theSingularityRequestHistory
s in a specific time range, this change allows us to get the request history entries filtered bycreatedBefore
andcreatedAfter
times via SingularityClient#getHistoryForRequest