Yes, I specifically was addressing the /select handler, sorry about not
mentioning it explicitly. My use case was, originally, with CloudSolrStream in
SolrJ, where I could observe the same behaviour and I created the streaming
expression in the UI to test if it was SolrJ-specific.
> On 21 Jun 2
Thanks a lot for the clarification. I created a Jira ticket not to lose track
of this:
https://issues.apache.org/jira/browse/SOLR-12510
> On 21 Jun 2018, at 20:53, Joel Bernstein wrote:
>
> That is actually the current behavior of the search expression. The initial
> use cases from Streaming E
So I think 2 things are being missed here. You should be specifying the
qt=“/export” to see all the results.
If you do not do that, then the select handler is used by default which gives
the default 10-20 rows as result.
> On Jun 21, 2018, at 12:53 PM, Joel Bernstein wrote:
>
> That is actuall
That is actually the current behavior of the search expression. The initial
use cases from Streaming Expressions revolved around joins and rollups
which really require the entire result set. So the search expression just
merged the results from the shards and let the wrapping expression deal
with t
