The customer creates a patch for deploying with Alfresco during bootstrap that creates categories which are used in classification rules.
The problem is the patch executes during the Alfresco bootstrap. It tries to create a root category using CategoryService and it performs a query on "PATH:/cm:categoryRoot/cm:generalclassifiable". Such a query cannot be performed on the database and must therefore use Solr. But since Solr is unavailable at this point (noindex mode), an exception is thrown in the bootstrap.
The customer would like CategoryService enhanced to allow db queries - this would allow their patch to be deployed in the bootstrap.
See a previous case in
MNT-10670 which was closed with "won't fix".
Customer need to use CategoryService in a patch (so during bootstrap) because they create business categories. Those categories are used in classification rules. If they ask the customer to create the categories manually, there will surely be mis-spelling between the different environments (dev, integration, production). So the categories and the rules are created by patch to avoid human error.
It will also go in the way of Alfresco to move most request in database query in order to improve consistency and performance.