Reported by Shawn Pearce <sop@google.com> on Fri Jan 16 18:17:45 PST 2009
Source: JIRA GERRIT-26
Affected Version: 2.0
ChangeListService's allOpenPrev, allOpenNext, allClosedPrev, allClosedNext
methods can generate queries which scan the changes table. If the user is
anonymous, or even if they are logged in but the majority of the changes
aren't visible to the user these methods can take a long time to respond as
they may need multiple batches of data from the database in order to fill up
the page requested by the client.
We should try to detect if there is a good chance that for this user the
changes are spread very far apart and increase the size of the query window,
or simply reject the query request altogether (especially in the anonymous
user case).
Owner: s...@google.com