[ 
https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482734#comment-13482734
 ] 

Chris Russell commented on SOLR-2894:
-------------------------------------

In my experience using this patch, it seems that it does not over-request when 
enforcing a limit?
This is problematic because, for example, in a situation where you have many 
slaves and you are pivoting on a fairly evenly distributed field and setting 
your facet limit to X, the Xth distinct value for that field by document count 
on each slave is likely to be different.  The result is that some facet values 
close to your limit boundary will not get reported for aggregation, which will 
make your ultimate results somewhat inaccurate.

It was my impression that other facet-based features of solr over-request when 
there is a limit to combat this situation?  For example if you specify limit 
10, the distributed query might have limit 100 or 1000, and then during 
aggregation it would be limited to the top 10.

I am working on similar functionality for this patch.
                
> Implement distributed pivot faceting
> ------------------------------------
>
>                 Key: SOLR-2894
>                 URL: https://issues.apache.org/jira/browse/SOLR-2894
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Erik Hatcher
>             Fix For: 4.1
>
>         Attachments: distributed_pivot.patch, distributed_pivot.patch, 
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894-reworked.patch
>
>
> Following up on SOLR-792, pivot faceting currently only supports 
> undistributed mode.  Distributed pivot faceting needs to be implemented.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to