[
https://issues.apache.org/jira/browse/SOLR-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674584#action_12674584
]
Peter Wolanin commented on SOLR-1022:
-------------------------------------
The "ignored" field is non-indexed and non-stored. The suggested function in
the example schema.xml is to avoid Solr errors when there is a doc field that
matches nothing in the schema.
I found that the one in the example schema being single-valued, if I send in an
unmatched multi-valued field I still get the error that enabling this field was
intended to prevent.
I did not send to the ML, since this seemed pretty trivial, but I can do so as
well.
> suggest multiValued for ignored field
> -------------------------------------
>
> Key: SOLR-1022
> URL: https://issues.apache.org/jira/browse/SOLR-1022
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.3
> Environment: Mac OS 10.5 java 1.5
> Reporter: Peter Wolanin
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1022.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> We are actually using the suggested "ignored" field in the schema. I have
> found, however, that Solr still throws a error 400 if I send in an unmatched
> multi-valued field.
> It seems that if I set this ignored field to be multiValued than a document
> with unrecognized single or multiple value fields is sucessfully indexed.
> Attached patch alters this suggested item in the schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
