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

Dennis Gove edited comment on SOLR-8409 at 2/4/16 2:54 AM:
-----------------------------------------------------------

I believe if it were changed to 
{code}
text="XXXX XXXX"
{code}
it would trip the failure. The issue is with double quotes because double 
quotes are used to wrap the parameter values. So a q param of
{code}
search(....., q="text:\"XXXX XXXX\"", ..... )
{code}
would show the issue.

The issue is that the q param given to Solr cannot include the \" and should 
instead include just the " around XXXX XXXX. So, to deal with that we have to 
replace \" with ". That then also requires that on the toExpression(...) we 
have to replace " with \".


was (Author: dpgove):
I believe if it were changed to 
{code}
text="XXXX XXXX"
{code}
it would trip the failure. The issue is with double quotes because double 
quotes are used to wrap the parameter values. So a q param of
{code}
search(....., q="text:\"XXXX XXXX\"", ..... )
{code}
would show the issue.

> Complex q param in Streaming Expression results in a bad query
> --------------------------------------------------------------
>
>                 Key: SOLR-8409
>                 URL: https://issues.apache.org/jira/browse/SOLR-8409
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrJ
>    Affects Versions: Trunk
>            Reporter: Dennis Gove
>            Priority: Minor
>              Labels: streaming, streaming_api
>         Attachments: SOLR-8409.patch, SOLR-8409.patch
>
>
> When providing an expression like 
> {code}
> stream=search(people, fl="id,first", sort="first asc", 
> q="presentTitles:\"chief executive officer\" AND age:[36 TO *]")
> {code}
> the following error is seen.
> {code}
> no field name specified in query and no default specified via 'df' param
> {code}
> I believe the issue is related to the \" (escaped quotes) and the spaces in 
> the q field. If I remove the spaces then the query returns results as 
> expected (though I've yet to validate if those results are accurate).
> This requires some investigation to get down to the root cause. I would like 
> to fix it before Solr 6 is cut.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to