If you search in resultsdb frontend for results which are a) not there b) not fresh enough (too long in the past), the whole query will most likely time out and you won't see anything. E.g. if there are only 5 results for task-foo, but you request a page with 10 of them (the default), you won't see nothing and a page will time out.
After discussion with @jskladan, it seems reasonable to put a default time constraint to resultsdb_frontend to limit the search to some interval (what about 30 days back?). The initial implementation could simply put the time restraint in URL, a follow-up could show a setting in the search UI.
Metadata Update from @kparal: - Issue tagged with: easyfix
Actually since argument works on results endpoint, results?since=2018-06-28,2018-07-03 for example . Will be enough to set a default 30 day back since argument to the search form?
since
results?since=2018-06-28,2018-07-03
There's a PR in #11. I believe since is fit exactly for this, but I'll let @jskladan reply.
since works since current implementation forwards all the results arguments to resultsdb.
On this PR I added a default value of last 30 days to since and an UI to modify it on search form
Commit 13cdad0 fixes this issue
Login to comment on this ticket.