Hoss, Thanks for the update. Any idea how to handle this exact query (which was giving no results before upgrade and now gives error and pushes query to a big loop for maxBooleanClauses issue ) , Many regards.
http://localhost:8983/solr/techproducts/select?start=0&rows=0&defType=edismax&pf=title+nouns+synonyms&ps=5&debugQuery=true&q=(ccoco%25e2%2580%2586oco%25e2%2580%2586o%25e2%2580%2586mco%25e2%2580%2586o%25e2%2580%2586mco%25e2%2580%2586o) On Tue, Nov 7, 2023 at 12:50 PM Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : Mikhail, Thanks for the comment. Is this considered a bug or as a new > : feature with no plan to address this type of query expansion in further > : releases? > > It is a documented feature in Lucene (to prevent query explosion) with the > change in behavior called out in the "Major Changes" section of the > Solr upgrade notes when the behavior was changed in Solr 9.0... > > > https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#querying-and-indexing-2 > > "solr.xml maxBooleanClauses is now enforced recursively. Users who upgrade > from prior versions of Solr may find that some requests involving complex > internal query structures (Example: long query strings using edismax with > many qf and pf fields that include query time synonym expansion) which > worked in the past now hit this limit and fail. Users in this situation > are advised to consider the complexity of their queries/configuration, and > increase the value of maxBooleanClauses if warranted." > > > -Hoss > http://www.lucidworks.com/ >
