Repair - Rebuild repository search queries are not optimized, potentially impacting other search operations

Problem

When running the "Repair - Rebuild repository search" task, a single poor performing query is pulling all components from a repository. This is retrieving too much data at once, which can impact other search operations like keyword searches.

Expected

Adjust single query to Instead batch process the components.

Allow expensive searches ( usually keyword based ) to execute without consuming disproportionate resources.

Provide a separate "Search request timeout" for searches in the Administration -> System -> Capabilities -> UI: Settings -> Settings screen. This timeout value could be adjusted to a fixed value by an administrator in extreme cases where long running or expensive searches still occur. The default UI search timeout if not adjusted will be 5 seconds less than the "Standard request timeout" value.