Description
Stats component currently computes all stats (except for one) every time because they are relatively cheap, and in some cases dependent on eachother for distrib computation – but if we start layering stats on other things it becomes unnecessarily expensive to compute all the stats when they just want the "sum" (and it will definitely become excessively verbose in the responses).
The plan here is to use local params to make this configurable. All of the existing stat options could be modeled as a simple boolean param, but future params (like percentiles) might take in a more complex param value...
Example:
stats.field={!min=true max=true percentiles='99,99.999'}price
stats.field={!mean=true}weight
Attachments
Attachments
Issue Links
- incorporates
-
SOLR-6682 EnumField + StatsComponent gives bad toString() for min/max, probably doesn't work in distributed search ... definitely needs more tests
-
- Closed
-