[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Johnson updated SOLR-217:
------------------------------
Attachment: ignoreNonIndexedNonStoredField.patch
I like that solution and I can definitely see the advantages of having
dumb_*=ignored and so on. How does this patch sound instead of the
previous:
public Field createField(SchemaField field, String externalVal, float
boost) {
String val;
try {
val = toInternal(externalVal);
} catch (NumberFormatException e) {
throw new SolrException(500, "Error while creating field '" +
field + "' from value '" + externalVal + "'", e, false);
}
if (val==null) return null;
if (!field.indexed() && !field.stored()) {
log.finest("Ignoring unindexed/unstored field: " + field);
return null;
}
... blah blah blah....
- will
> 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: ignoreNonIndexedNonStoredField.patch,
> 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.
