For change queries ChangeIndexRewriter checks that the number of terms
in the query does not exceed the max terms that are configured by
index.maxTerms. AccountIndexRewriter now does this check too. In
addition we do the check in ReviewersUtil which bypasses
AccountIndexRewriter by doing a raw index query.
The new test verifies that the max terms check is done when suggesting
reviewers. However if max terms is exceeded that REST endpoint doesn't
fail, but returns an empty result. This is because ReviewersUtil catches
any QueryParseException and returns an empty result (that might be
reconsidered, but not in this change).
Change-Id: I6f83da758e9279ae85b2c0020e4ee9856b44bef8
Signed-off-by: Edwin Kempin <ekempin@google.com>
c702fb337d