Background: We have a multi-tenant AEM Assets environment with two brands, where either brand users can't see each others assets including in omni search results (managed through Permissions). We currently have a taxonomy like /content/dam/brand-1/.. and /content/dam/brand-2/.. They both share the same metadata schema and we don't have any cross-brand user use-cases.
Problem statement: Brand-2 has search requirements that are contradictory to Brand-1. For e.g. Brand-1 should NOT be able to search the keyword against a particular metadata property while Brand-2 should be. Hence, we have a situation where we can't handle both search requirements using one custom search index definition (?) and there's also no way to explicitly define which Index to pick per content path or per User/group (?)
So, I would like to know your views on possible solutions ?
You are correct, Omnisearch Asset Search Rail is global across all tenants. There are 2 main (custom) ways to "tenantize" it's behavior.
The first is to ACL the search predicate fields nodes for the Omnisearch rail under /conf/global/... Obviously, this will not satisfy your requirement, since your requirement is to disallow Fulltext terms to be evaluated against specific JCR properties.