[
https://issues.apache.org/jira/browse/SOLR-14518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118178#comment-17118178
]
Joel Bernstein edited comment on SOLR-14518 at 5/28/20, 12:44 AM:
------------------------------------------------------------------
There are two frequently used approaches to co-locate records on the same
shard, one is block join and the other is composite id routing. This would
provide fast distributed unique functionality on the routing key for those that
are using composite id routing.
was (Author: joel.bernstein):
There are two frequently used approaches to co-locate records on the same
shard, one is block join and the other is composite id routing. This would
provide fast unique functionality on the routing key for those that are using
composite id routing.
> Add support for partitioned unique agg to JSON facets
> -----------------------------------------------------
>
> Key: SOLR-14518
> URL: https://issues.apache.org/jira/browse/SOLR-14518
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Facet Module
> Reporter: Joel Bernstein
> Priority: Major
>
> There are scenarios where documents are partitioned across shards based on
> the same field that the *unique* agg is applied to with JSON facets. In this
> scenario exact unique counts can be calculated by simply sending the bucket
> level unique counts to the aggregator where they can be summed. Suggested
> syntax is to add a boolean flag to the unique aggregation function:
> *unique*(partitioned_field, true).
> The *true* value turns on the "partitioned" unique logic. The default is
> false.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
