Remove the assumption from org.hibernate.search.integrationtest.mapper.orm.search.loading.SearchQueryEntityLoadingFetchSizeIT#checkFetchSizeSupported once this is implemented, as we will probably use the fetch size to determine the number of queries to execute?
CriteriaObjectsInitializer already takes care of the case that some databases only support a limited amount of entries per IN clause. However, in some databases there exists also a overall limit of parameter which can be set per query, eg SQLServer.
See also: https://forum.hibernate.org/viewtopic.php?f=9&t=1013066 and
I think both mechanisms should be at play BTW. The IN clause max and the total max to keep it as efficient as possible
Targeting 6.0.0, because we didn't restore the limit for the amount of entries per IN clause yet, and I'd rather fix everything simultaneously.