If you have many Full text fields and are using a View that searches for "multiple words" there are changes (like after 5 years, never seen that before) you will hit
org.apache.lucene.search.IndexSearcher$TooManyNestedClauses: Query contains too many nested clauses; maxClauseCount is set to 1024 => org.apache.lucene.search.IndexSearcher$TooManyNestedClauses: Query contains too many nested clauses; maxClauseCount is set to 1024
The reason is Drupal will split your phrase by spaces, and query each word against every field. But also use the language specific and the _und_ fields Imagine the combination == larger than 1024 boolean clauses
Solr allows to bump that number. Still in production I would not recommend to simply sent to all Full text fields every word.
What?
If you have many Full text fields and are using a View that searches for "multiple words" there are changes (like after 5 years, never seen that before) you will hit
org.apache.lucene.search.IndexSearcher$TooManyNestedClauses: Query contains too many nested clauses; maxClauseCount is set to 1024 => org.apache.lucene.search.IndexSearcher$TooManyNestedClauses: Query contains too many nested clauses; maxClauseCount is set to 1024
The reason is Drupal will split your phrase by spaces, and query each word against every field. But also use the language specific and the
_und_fields Imagine the combination == larger than 1024 boolean clausesSolr allows to bump that number. Still in production I would not recommend to simply sent to all Full text fields every word.