[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492324
]
Yonik Seeley commented on SOLR-217:
-----------------------------------
This is a unique enough of a requirement, I'm not sure an additional
configuration switch is warranted.
However, another solution might be to allow fields to be unstored *and*
unindexed (essentially doing nothing). That would allow you to map a dynamic
field of "*" to an unstored + unindexed field.
It would also allow people to transition schemas + older clients. They could
change the old field to unstored + unindexed and use a copyField to move it to
the new field.
> 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.
