The current global search of SonarQube gets old and suffers from big performance issues as the database grows. Simply go and make a search on SonarQube.com to experience this bad situation.
As a user, when I search for a component (view, sub-view, project, module, file - main or test), I expect this global search to give me the results in less than a second.
Currently, the indexing is done through a dedicated table in the DB. This indexing should be done in Elasticsearch to benefit from all its power.
For this first MMF of the Epic
MMF-659, we'll concentrate on the performances only. In other words, to not have any dependency on the Web part, we expect the /api/components/suggestions WS to behave exactly the same way as in previous versions.
Obviously, this WS should be written in Java only so that the old Ruby-on-Rails implementation can be dropped.