You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default solr.xml does not contain a default entry for maxBooleanClauses.
This prevents the value to be set via javaOpts and forces uses to implement a custom config map with a custom solr.xml;
Adding <int name="maxBooleanClauses">${solr.max.booleanClauses:1024}</int> to the const DefaultSolrXML would not change the default values but would allow a simple override via the javaOpts
Probably a future version of the operator won't need to maintain a default solr.xml, if it can require a minimum solr version of 9.0. Since Solr v9.0 Solr will use a built-in default if no solr.xml is present in SOLR_HOME.
The Solr Operator currently supports Solr 7.7 (and 8.0), which do not have this option unfortunately, so we cannot add it by default.
We will soon release the next version of the Solr Operator and then we can increase the minimum version of Solr to 8.x (for some version of x), and this can be included in the next release. I'll get the ball rolling on this.
Since Solr v9.0 Solr will use a built-in default if no solr.xml is present in SOLR_HOME.
I am unbelievably excited for this when we have Solr 9.0 as a minimum version.
The default solr.xml does not contain a default entry for maxBooleanClauses.
This prevents the value to be set via javaOpts and forces uses to implement a custom config map with a custom solr.xml;
Adding
<int name="maxBooleanClauses">${solr.max.booleanClauses:1024}</int>
to theconst DefaultSolrXML
would not change the default values but would allow a simple override via the javaOptsbasically the change is solr_util.go
The text was updated successfully, but these errors were encountered: