Hi Jason,
Thanks a lot for the post. Indeed the web page you are referring to has
some very nice examples. Well done.
Cheers,
Arturas
Increasing the number of threads (through the url or params section) is
unsuccessful so far. Maybe solr takes it only as a hint.
On Thu, Dec 10, 2020 at 8:01 PM
Hey Arturas,
Can't help you with the secrets of Michael's inspiration (though I'm
also curious :-p). And I'm not sure if there's any equivalent of
facet.threads for JSON Faceting. You're on your own there
unfortunately.
But you (or other readers) might find this "Query Facet" example handy
- it
Hi Michael,
I wish I were able to do a percent of what you are doing. Where does your
inspiration come from? It is not from the manuals, cause I've checked
those. How do you come up with this piece of art? Did you check this from
the source code? Which lines revealed these secrets? I am eternally
I think the first "error" case in your set of examples above is closest to
being correct. For "query" facet type, I think you want to explicitly
specify `"type":"query"`, and specify the query itself in the `"q"` param,
i.e.:
{
"query" : "*:*",
"limit" : 0,
"facet": {
"aip":
Hi Michael,
Thanks for helping me to figure this out.
If I fire:
{
"query" : "*:*",
"limit" : 0,
"facet": {
"aip": { "query": "cfname2:aip", }
}
}
I get
"response": { "numFound": 20560849, "start": 0, "numFoundExact": true,
"docs": [] }, "facets": { "count": 205608
Arturas,
I think your syntax is wrong for the range subfacet? -- the configuration
of the range facet should be directly under the `tt` key, rather than
nested under `t_buckets` in the request. (The response introduces a
"buckets" attribute that is not part of the request syntax).
Michael
On Thu,
