ANW-1134: Avoid resolving top_containers where it's unnecessary #2708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove 'top_container_uri_u_sstr:id' from default search opts in
controllers where it isn't required / used.
Not only is it unnecessary but it can wreak havoc in general
searches where the search returns records containing many
instances, resulting in "too many boolean clauses".
For the latter issue we now pre-check for subqueries that
exceed our defined limit (default 1024) and drop the excess
conditions with a warning, equivalent to the max resolve warning.
Checklist: