[
https://issues.apache.org/jira/browse/SOLR-15053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-15053:
-------------------------------------
Component/s: documentation
> Remove ref-guide preference for collapse over grouping
> ------------------------------------------------------
>
> Key: SOLR-15053
> URL: https://issues.apache.org/jira/browse/SOLR-15053
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jason Gerlowski
> Priority: Major
>
> Currently, the ref-guide states a clear preference for collapse over grouping.
> bq. Generally, you should prefer Collapse & Expand.
> But the reality is more complicated. Collapse grouping has a lot of
> limitations on when it can be used (single shard environments only, with the
> exception that multi-shard environments can be made to work by ensuring that
> each value in the grouping field is colocated within the same shard.
> Further, it's not necessarily more or less performant than traditional
> grouping:
> As Joel Bernstein put it in a recent mailing list thread:
> bq. There is a very specific use case where collapse performs better and in
> these scenarios collapse might be the only option that would work. The use
> case where collapse works better is: (1) High cardinality grouping field,
> like product id, (2) Larger result sets, (3) The need to know the full number
> of groups that match the result set. In grouping this is group.ngroups. At a
> certain point grouping will become too slow under the scenario
> described above. It will all depend on the scale of #1 and #2 above.
> We should correct the ref-guide wording here, as it's misleading for novice's
> and experts alike.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
