[
https://issues.apache.org/jira/browse/SOLR-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493937#comment-15493937
]
David Smiley commented on SOLR-9517:
------------------------------------
I think I ran into this and discovered what was going on via debugging... it's
very confusing to the user as there is no error. We should throw an error if
'qf' refers to invalid fields.
> Add apparent hint for nullified query caused by invalid QF
> ----------------------------------------------------------
>
> Key: SOLR-9517
> URL: https://issues.apache.org/jira/browse/SOLR-9517
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 3.6, 5.4
> Reporter: Peter Liu
> Priority: Minor
>
> When query with a invalid field in QF, the query text will not be
> parsed/interpreted in Lucene's syntax: All Boolean Operator will be treated
> as raw text for searching.
> For Example: I misspelled a field name,"product_labels", by missing suffix
> "s" in QF , and the query was "cpu AND amd". I enabled debuqQuery and found
> the "AND" is analyzed and tokenized as raw text. which was supposed to be
> treated as Boolean Operator.
> I spend half an hour to google it but nothing helpful(at the beginning I
> thought there's something like "syntax switch" was turned off by mistake).
> not critical , It does bother.
> (at least) We should add indicator like "partialResults" in the response. OR
> reject the query and return 400 directly, evidencing the bug in application
> layer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
