You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/11/04 19:28:28 UTC

[jira] [Commented] (SOLR-8222) Optimize count-only faceting when there are many expected matches-per-ord

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

ASF subversion and git services commented on SOLR-8222:
-------------------------------------------------------

Commit 1712608 from [~yonik@apache.org] in branch 'dev/trunk'
[ https://svn.apache.org/r1712608 ]

SOLR-8222: optimize method=dv faceting for counts

> Optimize count-only faceting when there are many expected matches-per-ord
> -------------------------------------------------------------------------
>
>                 Key: SOLR-8222
>                 URL: https://issues.apache.org/jira/browse/SOLR-8222
>             Project: Solr
>          Issue Type: Improvement
>          Components: Facet Module
>            Reporter: Yonik Seeley
>            Assignee: Yonik Seeley
>         Attachments: SOLR-8222.patch, SOLR-8222.patch, SOLR-8222.patch
>
>
> This optimization for the JSON Facet API came up a few months ago on the mailing list (I think by Toke).
> Basically, if one expects many hits per bucket, use a temporary array to accumulate segment ords and map them all at the end to global ords.  This saves redundant segOrd->globalOrd mappings at the cost of having to scan the temp array.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org