Hallo all,

the default solrconfig.xml fpr Solr 9.8.1 declares

  <updateProcessor class="solr.NumFieldLimitingUpdateRequestProcessorFactory" 
name="max-fields">
    <int name="maxFields">1000</int>
    <bool name="warnOnly">true</bool>

which is used in

  <updateRequestProcessorChain name="add-unknown-fields-to-the-schema" 
default="${update.autoCreateFields:true}"
           
processor="uuid,remove-blank,field-name-mutating,max-fields,parse-boolean,parse-long,parse-double,parse-date,add-schema-fields">
    <processor class="solr.LogUpdateProcessorFactory"/>
    <processor class="solr.DistributedUpdateProcessorFactory"/>
    <processor class="solr.RunUpdateProcessorFactory"/>
  </updateRequestProcessorChain>

The documentation states that the Attribute warnOnly defines whether the 
situation of having too many fields ends in a warning or in an error.
As you can see the configurations says

<bool name="warnOnly">true</bool>

When we call the /update API on a collection exceeding that fieldcount  we get 
an error 400 and not only a warning.

Can someone explain that behaviour to me. Or is there a bug between the 
processing output and the REST-API-Wrapper?

Hints welcome.

Best regards
Andreas

Reply via email to