On Mon, Dec 28, 2015 at 9:11 AM, Joel Bernstein wrote:
> In
> order to join result sets you would typically need to be working with the
> entire result sets from both sides of the join, which may be too slow
> without the /export handler.
We now have https://issues.apache.org/jira/browse/SOLR-822
Yes that would work. Each search(...) has it's own specific params and can
point to any handler that conforms to the output format in the /select
handler.
Joel Bernstein
http://joelsolr.blogspot.com/
On Mon, Dec 28, 2015 at 11:12 AM, Dennis Gove wrote:
> Correct me if I'm wrong but I believe o
Correct me if I'm wrong but I believe one can use the /export and /select
handlers interchangeably within a single streaming expression. This could
allow you to use the /select handler in the search(...) clause where a
score is necessary and the /export handler in the search(...) clauses where
it i
I'll add one important caveat:
At this time the /export handler does not support returning scores. In
order to join result sets you would typically need to be working with the
entire result sets from both sides of the join, which may be too slow
without the /export handler. But if you're working w
There have been a lot of new features added to the Streaming API and the
documentation hasn't kept pace, but it is something I'd like to have filled
in by the release of Solr 6.
With the Streaming API you can take two (or more) totally disconnected
collections and get a result set with documents f
In Solr 5.1.0 we had to flatten out two collections into one
Item - about 1.5 million items with primary key - ItemId (this mainly
contains item description)
FacilityItem - about 10,000 facilities - primary key - FacilityItemId
(pricing information for each facility) - ItemId points to Item
We a
