[
https://issues.apache.org/jira/browse/SOLR-7461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-7461.
----------------------------
Resolution: Fixed
Fix Version/s: 5.2
6
NOTE: final commit differed slightly from the lsat patch i posted: I cleaned up
some exception logging in the distrib test, and simplified how/where
statsToCalculate was getting updated.
(neither of which is directly realted to this issue, but i noticed them while
reviewing the patch again)
> StatsComponent, calcdistinct, ability to disable distinctValues while keeping
> countDistinct
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-7461
> URL: https://issues.apache.org/jira/browse/SOLR-7461
> Project: Solr
> Issue Type: Improvement
> Reporter: James Andres
> Assignee: Hoss Man
> Labels: statscomponent
> Fix For: 6, 5.2
>
> Attachments: SOLR-7461.patch
>
>
> When using calcdistinct with large amounts of data the distinctValues field
> can be extremely large. In cases where the countDistinct is only required it
> would be helpful if the server did not return distinctValues in the response.
> I'm no expert, but here are some ideas for how the syntax could look.
> {code}
> # Both countDistinct and distinctValues are returned, along with all other
> stats
> stats.calcdistinct=true&stats.field=myfield
> # Only countDistinct and distinctValues are returned
> stats.calcdistinct=true&stats.field={!countDistinct=true
> distinctValues=true}myfield
> # Only countDistinct is returned
> stats.calcdistinct=true&stats.field={!countDistinct=true}myfield
> # Only distinctValues is returned
> stats.calcdistinct=true&stats.field={!distinctValues=true}myfield
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
