[
https://issues.apache.org/jira/browse/SOLR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366063#comment-14366063
]
Shawn Heisey edited comment on SOLR-3923 at 3/17/15 11:16 PM:
--------------------------------------------------------------
I don't know when this particular problem got fixed, probably after SOLR-3377,
but it does seem to be fixed now.
There is however still some strangeness when those spaces that I mentioned are
added:
With this query parameter (which has the spaces around the first clause):
{noformat}
(( special_cats:string1 ) (Kitchen Sink))
{noformat}
I get this parsed query:
{noformat}
+((special_cats:string1 ((catchall:kitchen)~0.1 (catchall:sink)~0.1))~2)
(catchall:"? ? kitchen sink"~3^2.0)~0.1
{noformat}
Note the two question marks.
If I take the spaces out around the first query clause, then it does what I
expect:
{noformat}
+((special_cats:string1 ((catchall:kitchen)~0.1 (catchall:sink)~0.1))~2)
(catchall:"kitchen sink"~3^2.0)~0.1
{noformat}
This is on Solr 4.9.1.
was (Author: elyograg):
I don't know when this particular problem got fixed, probably after SOLR-3377,
but it does seem to be fixed now.
There is however still some strangeness when those spaces that I mentioned are
added:
With this query parameter (which has the spaces around the first clause):
{noformat}
(( special_cats:string1 )+(Kitchen+Sink))
{noformat}
I get this parsed query:
{noformat}
+((special_cats:string1 ((catchall:kitchen)~0.1 (catchall:sink)~0.1))~2)
(catchall:"? ? kitchen sink"~3^2.0)~0.1
{noformat}
Note the two question marks.
If I take the spaces out around the first query clause, then it does what I
expect:
{noformat}
+((special_cats:string1 ((catchall:kitchen)~0.1 (catchall:sink)~0.1))~2)
(catchall:"kitchen sink"~3^2.0)~0.1
{noformat}
This is on Solr 4.9.1.
> eDismax: complex fielded query with parens is not recognized
> ------------------------------------------------------------
>
> Key: SOLR-3923
> URL: https://issues.apache.org/jira/browse/SOLR-3923
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 3.5
> Reporter: Shawn Heisey
> Fix For: 3.6.3
>
>
> This is similar to SOLR-3377. That bug appears to have fixed this problem
> for 4.x.
> I can see the effects of SOLR-3377 when I test a query similar to below on
> the Solr 3.6 example, which is expected because SOLR-3377 was found in 3.6
> but only fixed in 4.0. This bug is a little different, and exists in 3.5.0
> for sure, possibly earlier. The first part of the parsed query looks right,
> but then something weird happens and it gets interpreted as a very strange
> phrase query.
> query URL sent to solr 3.5.0 example:
> {code}http://localhost:8983/solr/collection1/select?q=%28%28cat%3Astring1%29+%28Kitchen+Sink%29%29&wt=xml&debugQuery=true&defType=edismax&qf=text&pf=text^2.0
> {code}
> parsedquery_toString:
> {code}+((cat:string1 ((text:kitchen) (text:sink)))~2) (text:"cat:string1
> kitchen sink"^2.0)
> {code}
> Adding some spaces before and after cat:string1 fixes it:
> {code}http://localhost:8983/solr/collection1/select?q=%28%28%20cat%3Astring1%20%29+%28Kitchen+Sink%29%29&wt=xml&debugQuery=true&defType=edismax&qf=text&pf=text^2.0
> {code}
> {code}+((cat:string1 ((text:kitchen) (text:sink)))~2) (text:"kitchen
> sink"^2.0)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
