[TMP] IBX-11146: Updated filtering logic to use LanguageCode criterion with {terms} clause

[ViniTou]

🎫 Issue	IBX-11146

Related PRs:

• IBX-11146: Test for solr search with many (50+) languages core#703
• IBX-11146: Test with new test case (this should fail) #108

Description:

Problem

When many languages are configured in Ibexa (e.g., >20-30), the language fallback logic in NativeCoreFilter generates an exponentially growing number of boolean clauses. This causes Solr queries to fail with a maxBooleanClauses error (default limit is 1024).
The problematic query structure for exclusion was:
NOT (content_language_codes_ms:"lang1" OR content_language_codes_ms:"lang2" ...)
For a fallback chain, this exclusion is repeated for every priority level, leading to O(N^2) complexity in clause count.

Solution

Optimized the query generation to use Solr's Terms Query Parser ({!terms}) for language exclusions. This parser treats a list of values as a single query clause, regardless of the number of elements.
The new query structure is:
_query_:"{!terms f=content_language_codes_ms}lang1,lang2..."
This reduces the complexity from O(N^2) boolean clauses to O(N) single clauses, effectively bypassing the maxBooleanClauses limit for this use case.

Applies strtolower() to values because the Terms parser bypasses analysis, but the underlying field (content_language_codes_ms) is lowercased in the schema.

For QA:

Dont focus at the 50 languages thing - check if site access combinations languages work properly, take alwaysAvailable flag into consideration, fallback, default languages and so on.

Documentation:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud