[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131579#comment-15131579
]
Joel Bernstein commented on SOLR-8409:
--------------------------------------
Just tried to trip this bug with this test case:
{code}
params.put(CommonParams.QT, "/sql");
params.put("numWorkers", "2");
params.put("stmt", "select str_s, count(*), sum(field_i), min(field_i),
max(field_i), avg(field_i) from collection1 where text='XXXX XXXX' group by
str_s order by sum(field_i) asc limit 2");
{code}
This would have a query like this: text:"XXXX XXXX" which would be serialized
and sent to workers. It works, so somehow the serialization was handling
things.
> 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]
