[jira] [Commented] (SOLR-5163) edismax gobbles exceptions for unrelated issues

["Cassandra Targett (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322406#comment-16322406 ] 

Cassandra Targett commented on SOLR-5163:
-----------------------------------------

I can reproduce this with the techproducts example docs. Index them, then do a query like:

{{debugQuery=on&defType=edismax&q=storm%20AND%20sword&qf=name^2.0&qf=series^2.0}}

(where the field "series" for the 2nd {{qf}} is the field that doesn't exist)

The parsedquery from the debug output is: 

{{+(DisjunctionMaxQuery(((name:storm)^2.0)) DisjunctionMaxQuery(((name:and)^2.0)) DisjunctionMaxQuery(((name:sword)^2.0)))}}

If you use a field that does exist, like "series_t", instead you get a parsedquery like:

{{+(+DisjunctionMaxQuery(((name:storm)^2.0 | (series_t:storm)^2.0)) +DisjunctionMaxQuery(((name:sword)^2.0 | (series_t:sword)^2.0)))}}

The stranger thing is the query with the bad field name is the only one that returns the matching document.

> edismax gobbles exceptions for unrelated issues
> -----------------------------------------------
>
>                 Key: SOLR-5163
>                 URL: https://issues.apache.org/jira/browse/SOLR-5163
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers, search
>            Reporter: Steven Bower
>
> query:
> q=foo AND bar
> qf=field1
> qf=field2
> defType=edismax
> Where field1 exists and field2 doesn't..
> will treat the AND as a term vs and operator



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org