[
https://issues.apache.org/jira/browse/SOLR-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054004#comment-15054004
]
Dennis Gove commented on SOLR-8409:
-----------------------------------
Backing up my hunch is that if I change the q to be
{code}
presentTitles:\"chief\" AND age:[36 TO *]
{code}
I get results back but a very small subset of the results I would expect to
get back.
I've yet to visually verify the source data but I would guess that there is a
record containing a field value
<presentTitles>"chief"</presentTitles>
I'll check for that the next time I'm looking into this (by Monday I suspect)
but I'd wager that I'll find it.
> 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: [email protected]
For additional commands, e-mail: [email protected]
