Christine Poerschke created SOLR-14939:
------------------------------------------
Summary: JSON facets: range faceting to support cache=false
parameter
Key: SOLR-14939
URL: https://issues.apache.org/jira/browse/SOLR-14939
Project: Solr
Issue Type: Bug
Reporter: Christine Poerschke
Assignee: Christine Poerschke
The {{cache}} parameter, if set to {{false}}, is intended to support
non-caching of the search results:
[https://lucene.apache.org/solr/guide/8_6/common-query-parameters.html#cache-parameter]
Based on inspection of
{code:java}
curl
"http://localhost:8983/solr/admin/metrics?prefix=CACHE.searcher.filterCache"
{code}
metrics before and after a search we can see that range JSON facet queries
currently do not support a {{cache=false}} parameter.
Using the {{techproducts}} example collection as an illustration, if a 1 MONTH
{{gap}} value is used then 12 {{filterCache}} entries are added for a one year
{{start/end}} time range.
{code:java}
curl "http://localhost:8983/solr/techproducts/query?q=*:*&rows=0&cache=false"
-d 'json.facet={
manufacturedate_dt_ranges : {
type : range,
field : manufacturedate_dt,
mincount : 1,
gap : "%2B1MONTH",
start : "2005-01-01T00:00:00.000Z",
end : "2005-12-31T23:59:59.999Z",
}
}'
{code}
Similarly, if a 1 DAY {{gap}} value is used then 365 {{filterCache}} entries
are added for a one year {{start/end}} time range and if a 1 HOUR {{gap}} value
were to be used that would equate to 365 x 24 = 8,760 entries. This means that
a single search potentially displaces many or all existing {{filterCache}}
entries.
This ticket proposes to support the {{cache}} parameter for JSON range facet
queries:
* the current and default behaviour would remain {{cache=true}} and
* via {{cache=false}} users would be able run an 'uncommon' search with many
range buckets without impact on the 'common' searches with fewer range buckets.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]