[
https://issues.apache.org/jira/browse/SOLR-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Franke resolved SOLR-13894.
--------------------------------
Resolution: Not A Bug
> Solr 8.3 streaming expreessions do not return all fields (select)
> -----------------------------------------------------------------
>
> Key: SOLR-13894
> URL: https://issues.apache.org/jira/browse/SOLR-13894
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, streaming expressions
> Affects Versions: 8.3
> Reporter: Jörn Franke
> Priority: Major
>
> {color:#222222}I use streaming expressions, e.g.{color}
> {color:#222222}sortsSelect(search(...),id,if({color}{color:#222222}eq(1,1),Y,N)
> as found), by=“field A asc”){color}
> {color:#222222}(Using export handler, sort is not really mandatory , I will
> remove it later anyway){color}
> {color:#222222}This works perfectly fine if I use Solr 8.2.0 (server +
> client). It returns Tuples in the form \{ “id”,”12345”, “found”:”Y”}{color}
> {color:#222222}However, if I use Solr 8.2.0 as server and Solr 8.3.0 as
> client then the above statement only returns the id field, but not the
> "found" field.{color}
> {color:#222222}Questions:{color}
> {color:#222222}1) is this expected behavior, ie Solr client 8.3.0 is in this
> case not compatible with Solr 8.2.0 and server upgrade to Solr 8.3.0 will fix
> this?{color}
> {color:#222222}2) has the syntax for the above expression changed? If so
> how?{color}
> {color:#222222}3) is this not expected behavior and I should create a Jira
> for it?{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
