When I talk about efficiency I'm talking about computational and network
round trip efficiency. In it's regular setup Solr allows you to get the
documents and facets in a single request in one efficient call. If that's
the main use case using the standard Solr makes.
Streaming Expressions sacrific
We have a web site with traditional search capabilities, faceting, sorting
and so on. It has many problems before we took over and we need to
refectory it all. It has a single index for different type of documents,
and it has a very small amount of data.
The situation is that we are developing a P
It would be useful if you could describe your use case more fully. For
example are the users looking mainly for search results with facets? Or are
they looking for more flexibility and data analysis capabilities.
Streaming Expressions really lends itself to non-traditional search use
cases. If you
Amrit,
as far as I understand, in your example I have resulted documents
aggregated by the rollup function, but to get the documents themselves I
need to make another query that will get fq´s cached results, is that
correct?
And thanks for pointing about fq in Streaming Expression. I was looking
Kojo,
Not sure what do you mean by making two request to get documents. A
"search" streaming expression can be passed with "fq" parameter to filter
the results and rollup on top of that will fetch you desired results. This
maybe not mentioned in official docs:
Sample streaming expression:
expr=r
Hi,
I am working on PoC of a front-end web to provide an interface to the end
user search and filter data on Solr indexes.
I am trying Streaming Expression for about a week and I am fairly keen
about using it to search and filter indexes on Solr side. But I am not sure
whether this is the right ap
