This is a useful feature, but as in the old code, Solr didn't check the the validity in field and dynamicField in schema.xml.
So we extend Solr to add some custom parameters, such as
<field MYPARAM="VALUE" indexed="true" multiValued="true" name="f1" stored="true" type="string"/>
But after apply this patch, my code doesn't work any more.
– I think this should not be rare case as users usually need extend Solr - this is the good part of open source
I can change the code to make it work, but I think maybe we can add a parameter in schema.xml: validate=true/false in schema.xml level or in field/or dynamicField level, by default the value is true.
If users specify validate=false in schema.xml, field or dynamicField level, Solr will not validate trelated values.
In this way, users who extend Solr can easily makes their code works after upgrade.