But see Steve Rowe's comments at https://issues.apache.org/jira/browse/SOLR-4641 and use custom child properties as:
<field indexed="true" multiValued="true" name="f1" stored="true" type="string"> <MYPARAM>VALUE</MYPARAM> <!-- Maven property style --> <custom MYPARAM="VALUE"/> <!-- Alternative syntax; element name could be anything you want --> ... </field> Best Erick On Wed, Jun 12, 2013 at 6:49 PM, Erick Erickson <erickerick...@gmail.com> wrote: > bbarani: > > Where did you see this? I haven't seen it before and I get an error on > startup if I add validate="false" to a <field> definition.... > > Thanks, > Erick > > On Tue, Jun 11, 2013 at 12:33 PM, bbarani <bbar...@gmail.com> wrote: >> I think if you use validate=false in schema.xml, field or dynamicField level, >> Solr will not disable validation. >> >> I think this only works in solr 4.3 and above.. >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/SOLR-4641-Schema-now-throws-exception-on-illegal-field-parameters-tp4069622p4069688.html >> Sent from the Solr - User mailing list archive at Nabble.com.
