Code search is inefficient with space when indexing forks

Recently we have upgraded our Bitbucket Server. With this upgrade we've also obtained the code search feature based on Elastic search. Our /data partition on our Ubuntu server now has grown from 58G to 131G due to the size of the Elastic indices of 73G.

Is there a way to disable the search feature in total? Or wouldn't it a good idea to provide this option in the configuration?

Wouldn't it also be a good idea to have a settings section for code search on project and repository level? So it would be possible to disable indexing of a project or a repository?

Additionally, in some workflows forks can make up the bulk of the ES index. The ability to disable the indexing of forks would also decrease the index size for many setups.

In summary, this ticket suggests that Bitbucket Server implements:

• Configuration option to disable indexing (and search) entirely
• Configuration option to disable indexing of forks
• Configuration option to disable indexing at a repository and project level