[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Johnson updated SOLR-217:
------------------------------
Attachment: ignoreUnnamedFields.patch
the attached patch solve this problme by adding a new option to schema.xml to
allow unnamed fields including those that don't match dynamic fields to be
ignored. the default is false if the attribute is missing which is consistent
with existing SOLR functionality. if you want to enable this feature the
schema.xml would look like:
.... blah blah blah ...
<fields ignoreUnnamedFields="true">
.... blah blah blah ...
> 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.
