Elasticsearch with multiple limiting namespaces should be able to do a single code search across those indexed namespaces
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Elasticsearch Integration using Limiting namespaces and projects to index a few Groups (but not all) should be able to do a single code search across those indexed Groups.
Intended users
Further details
We already are able to search in indexed Groups. The dropdown to the right-hand side of the search text field does not allow multiple Groups selection. If that would be implemented we could trigger multiple Group searches and aggregate the results. This would also be the case for projects. This would enable customers to index only what they want to index. It can also help them save storage space on the Elasticsearch node which can be a pain-point with some customers. Also, searches could be faster and more targeted/scoped/granular (easier to use) since you can narrow down the search domain.
Proposal
Either a global search or a search that has the option to choose multiple Groups (and Projects) should be able to locate pattern hits across projects from different Groups (if those groups are indexed). This comes down to joining multiple existing (indexed) Group Code(as well as Commits and Wiki) Searches. The same goes for projects.
Documentation
Documentation changes would be minor even if we want to emphasise this as a great feature to keep that indexer size down.
What does success look like, and how can we measure that?
Customers that only choose a few namespaces to be indexed would be able to code search throughput that subset of namespaces. Right now customers can only search individual namespaces or index the entire instance and do a global code search.
What is the type of buyer?
This addresses mostly large customers who have large ES Indexes.