[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132259#comment-15132259
]
Joel Bernstein commented on SOLR-8409:
--------------------------------------
It took me while to grasp this ticket because it's so hard to reproduce the
exception. But I think I've got it now. Basically the instructions to users are:
If you have to use quotes in your query then escape the quotes:
{code}
search(collection1, q="blah \"stuff stuff\" blah", ...)
{code}
I'll do some more testing with the SQLHandler to make sure everything is
working properly with the quotes.
> 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: [email protected]
For additional commands, e-mail: [email protected]
