Thanks for bring closure to this. Yeah, “escaping hell” is something that
happens to us all, something that works in a browser doesn’t work
from SolrJ and neither one may work with curl and……
Pretty often, BTW, I look at the Solr log. It takes a little practice to
reconstruct the query, but it’s
Thanks for your reply! Yes, it turned out to be an issue with the way the
request was being sent, which was cURL that required special handling and
escaping of spaces and special characters. Using another client cleared
this issue and the request below worked perfectly now.
Best,
A.
On Thu, Jul
Might be a formatting error with my mail client, but the very first line is not
well formed.
q: * is incorrect
q=*:*
I do not see that example on the page either. Looks like you took the bit
that starts with stats=true and mis-typed the q clause.
Best,
Erick
> On Jul 3, 2019, at 5:08 AM,
Hi,
As per the documentation recommendation of using pivot with stats component
instead (
https://lucene.apache.org/solr/guide/8_1/faceting.html#combining-stats-component-with-pivots),
replacing the stats options that were previously used with the newer pivot
options as follows:
q: *
stats=true
Hi,
As per the documentation recommendation of using pivot with stats component
instead (
https://lucene.apache.org/solr/guide/8_1/faceting.html#combining-stats-component-with-pivots),
replacing the stats options that were previously used with the newer pivot
options as follows:
q: *
stats=true
Hi,
How can stats field value be calculated for top facet values? In other
words, the following request parameters should return the stats.field
measures for facets sorted by count:
q: *
wt: json
stats: true
stats.facet: authors_s
stats.field: average_rating_f
facet.missing: true
