So are you proposing that the DocumentBuilder check those properties on the field before it adds the field or do we need to add checks everywhere else to make sure nothing happens?
I'm happy to make either change and resubmit the patch. - will -----Original Message----- From: Erik Hatcher (JIRA) [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 12:11 PM To: solr-dev@lucene.apache.org Subject: [jira] Commented: (SOLR-217) schema option to ignore unused fields [ https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.p lugin.system.issuetabpanels:comment-tabpanel#action_12492332 ] Erik Hatcher commented on SOLR-217: ----------------------------------- I like Yonik's suggestion of allowing unstored+unindexed fields to be no-op. > schema option to ignore unused fields > ------------------------------------- > > Key: SOLR-217 > URL: https://issues.apache.org/jira/browse/SOLR-217 > Project: Solr > Issue Type: Improvement > Components: update > Affects Versions: 1.2 > Reporter: Will Johnson > Priority: Minor > Fix For: 1.2 > > Attachments: ignoreUnnamedFields.patch > > > One thing that causes problems for me (and i assume others) is that Solr is schema-strict in that unknown fields cause solr to throw exceptions and there is no way to relax this constraint. this can cause all sorts of serious problems if you have automated feeding applications that do things like SELECT * FROM table1 or where you want to add other fields to the document for processing purposes before sending them to solr but don't want to deal with 'cleanup' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
