[
https://issues.apache.org/jira/browse/SOLR-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011273#comment-13011273
]
Hoss Man commented on SOLR-2441:
--------------------------------
my gut reaction to ryan's initial issue was that it was a good idea, but the
other use case to consider is a schema that's changing over time.
if an existing client has a hardcoded list of fields they ask for:
"fl=id,name,summary,body" and i change my schema to make body no longer stored,
should that cause queries from that existing client to start failing? what if
i remove "summary" from the schema completely?
this almost feels like it should be configurable for the responsewriter's option
> Requesting invalid field names should return an error
> -----------------------------------------------------
>
> Key: SOLR-2441
> URL: https://issues.apache.org/jira/browse/SOLR-2441
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Fix For: 4.0
>
> Attachments: SOLR-2441-invalid-fl-error.patch,
> SOLR-2441-invalid-fl-error.patch
>
>
> If you send a request for *fl=foofoofoo* and that field does not exist, solr
> just returns empty documents:
> {code}
> <result name="response" numFound="17" start="0">
> <doc></doc>
> <doc></doc>
> <doc></doc>
> </result>
> {code}
> This seems like an error, not something we should support. (I think
> requesting an invalid field name should also be an error, but that is another
> issue)
> The distributed tests check if this is supported -- I don't think they should
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
