plone.api.content.find index validation is not appropriate in some implementations

https://github.com/plone/plone.api/blob/2.5.1/src/plone/api/content.py#L706 This section attempts to validate the query by making sure at least one ZCatalog index is present. However, some implementations remove the ZCatalog index in cases where querying on that index is only meant to be sent to a third party service like Elasticsearch. For example, wildcard.hps sends portal.portal_catalog(SearchableText="foo") to ES and encourages you to remove the SearchableText index from the ZCatalog as it would only take up space and increase index time.

But if that index is removed, api.content.find(SearchableText="foo") always returns an empty list.

What is the best solution here? Maybe an environment variable that can be set to skip the validate indexes step? Personally I do not see the benefit in the validation here in any case. If I call api.content.find() I would expect to get all content on the site, just as if I called portal.portal_catalog().

Start at src/plone/api/content.py#L706 and trace the index validation used by api.content.find(). Compare its behavior with portal.portal_catalog() when an index such as SearchableText is absent but queries may be handled by Elasticsearch. Done means agreeing on and documenting a solution that preserves valid third-party-backed queries without breaking catalog validation.