[ https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053981#comment-15053981 ]
Dennis Gove commented on SOLR-8409: ----------------------------------- I've been unable to replicate this in a unit test but have seen it in a fully packaged version of trunk. (ant package was run and then the tarball was unpacked). Differences between unit test and packaged version: * unit test is using dynamic fields while packaged version is using static fields * unit test is not going through the StreamHandler > 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, 6.0 > Reporter: Dennis Gove > Priority: Minor > Labels: streaming, streaming_api > > 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