lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Fanxi (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-792) Pivot (ie: Decision Tree) Faceting Component
Date Wed, 19 Oct 2011 09:10:11 GMT


Li Fanxi commented on SOLR-792:

I have a question about facet.pivot.mincount. Does this parameter defined as the limitation
for "minimum number of documents" that should be included in the result? 

In the current implementation, I found that this parameter also takes effect for the number
of facets fields, caused by the following code in doPivots function: 

    NamedList<Integer> nl = sf.getTermCounts(subField);
    if (nl.size() >= minMatch ) {
        pivot.add( "pivot", doPivots( nl, subField, nextField, fnames, rb, subset, minMatch
) );
        values.add( pivot ); // only add response if there are some counts

I don't understand why we need to compare minMatch to nl.size().

With this code, if we do pivot faceting on the fields "cat,manu_id_s", when cat='electronics'
and we have 50 documents distributed in 3 different "manu_id_s". If we limit the result with
facet.pivot.mincount=5, no result will be returned, because there are only 3 different "manu_id_s".
Is this the desired behavior for the "facet.pivot.mincount" parameter?
> Pivot (ie: Decision Tree) Faceting Component
> --------------------------------------------
>                 Key: SOLR-792
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Erik Hatcher
>            Assignee: Yonik Seeley
>            Priority: Minor
>         Attachments: SOLR-792-PivotFaceting.patch, SOLR-792-PivotFaceting.patch, SOLR-792-PivotFaceting.patch,
SOLR-792-PivotFaceting.patch, SOLR-792-as-helper-class.patch, SOLR-792-distributed.patch,
SOLR-792-raw-type.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch,
SOLR-792.patch, SOLR-792.patch
> A component to do multi-level faceting.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message