You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dennis Gove (JIRA)" <ji...@apache.org> on 2015/12/14 16:48:46 UTC

[jira] [Comment Edited] (SOLR-8409) Complex q param in Streaming Expression results in a bad query

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

Dennis Gove edited comment on SOLR-8409 at 12/14/15 3:48 PM:
-------------------------------------------------------------

This patch *appears* to fix the issues. Still am unable to replicate in a unit test but I have confirmed that the issue I was seeing in a packaged setup is fixed with this patch. 

I'll want to wait until I can get a replicated test before I commit this.


was (Author: dpgove):
This patch **appears** to fix the issues. Still am unable to replicate in a unit test but I have confirmed that the issue I was seeing in a packaged setup is fixed with this patch. 

I'll want to wait until I can get a replicated test before I commit this.

> 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
>         Attachments: 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org