lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Herrmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-6014) Nested subquery containing stop words only can invalidate whole query
Date Fri, 25 Apr 2014 13:30:16 GMT

     [ https://issues.apache.org/jira/browse/SOLR-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthias Herrmann updated SOLR-6014:
------------------------------------

    Description: 
org.apache.solr.request.StandardRequestHandler may parse the query string incorrectly when
"stop words" like "and" "in" etc... are used within nested subqueries.

Example query:
{{(((_query_:"\{!dismax qf=\"allfields\" \}transformation") AND (_query_:"\{!dismax qf=\"allfields\"
\}in")))}}

The parsed query is:
{{\+(\+(allfields:transform) ()) \+(\+() ())}}

The first subquery ("transformation") returns results but the second ("in") does not. The
term "in" is configured as stop word. 

Expected result:
The query should return the same results as returned by this query: {{(((_query_:"\{!dismax
qf=\"allfields\" \}transformation")))}}. Maybe one should just remove empty term lists?

This is probably related to SOLR-261.

  was:
org.apache.solr.request.StandardRequestHandler may parse the query string incorrectly when
"stop words" like "and" "in" etc... are used within nested subqueries.

Example query:
{{(((_query_:"\{!dismax qf=\"allfields\" \}transformation") AND (_query_:"\{!dismax qf=\"allfields\"
\}in")))}}

The parsed query is:
{{+(+(allfields:transform) ()) +(+() ())}}

The first subquery ("transformation") returns results but the second ("in") does not. The
term "in" is configured as stop word. 

Expected result:
The query should return the same results as returned by this query: {{(((_query_:"\{!dismax
qf=\"allfields\" \}transformation")))}}. Maybe one should just remove empty term lists?

This is probably related to SOLR-261.


> Nested subquery containing stop words only can invalidate whole query
> ---------------------------------------------------------------------
>
>                 Key: SOLR-6014
>                 URL: https://issues.apache.org/jira/browse/SOLR-6014
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>    Affects Versions: 4.2.1
>            Reporter: Matthias Herrmann
>
> org.apache.solr.request.StandardRequestHandler may parse the query string incorrectly
when "stop words" like "and" "in" etc... are used within nested subqueries.
> Example query:
> {{(((_query_:"\{!dismax qf=\"allfields\" \}transformation") AND (_query_:"\{!dismax qf=\"allfields\"
\}in")))}}
> The parsed query is:
> {{\+(\+(allfields:transform) ()) \+(\+() ())}}
> The first subquery ("transformation") returns results but the second ("in") does not.
The term "in" is configured as stop word. 
> Expected result:
> The query should return the same results as returned by this query: {{(((_query_:"\{!dismax
qf=\"allfields\" \}transformation")))}}. Maybe one should just remove empty term lists?
> This is probably related to SOLR-261.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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


Mime
View raw message