tree 8728ced500cbecfb3a8c3dae1edc00cc2328012f
parent 9a16e8c2643a9096ea1e6f585a0f68cf546e33c9
author Dave Borowitz <dborowitz@google.com> 1546622366 -0800
committer Dave Borowitz <dborowitz@google.com> 1547050389 -0800

Support related changes lists exceeding the user's query limit

Add a method to InternalQuery to exhaustively fetch a list of results
for multiple queries, and use this from InternalChangeQuery. For now, we
still respect the user's query limit because this always happens when we
set enforceVisibility=true. This may be revisited, but even so, the
queryExhaustively method is useful since the number of related changes
may also theoretically exceed the index's maxLimit.

As context, prior to Ibe271850, changes submitted with a rebase submit
strategy would be added to the relation chain of whatever change
happened to be at the tip of the branch, even if they weren't originally
related. This means even though users weren't creating chains of 500+
changes, they actually do exist in the wild due to this bug. Without
this change, GetRelated for those changes may fail with a 500 if the
input change didn't happen to show up in the first page of results in
the byProjectGroups query.

Change-Id: Ib9dad2454eed8110ce6db5e1bc840c59ebf82211