You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Sandro Martini (JIRA)" <ji...@apache.org> on 2013/03/08 23:11:15 UTC

[jira] [Commented] (PIVOT-899) Non-distributed pivot faceting conflict with facet.mincount and facet.pivot.mincount

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

Sandro Martini commented on PIVOT-899:
--------------------------------------

Excuse me, I don't understand what you are saying ... and in our code there isn't a reference to "getTermCounts".
Could you better explain ? Is it something related to our eclipse plugin ?
Thanks.

                
> Non-distributed pivot faceting conflict with facet.mincount and facet.pivot.mincount
> ------------------------------------------------------------------------------------
>
>                 Key: PIVOT-899
>                 URL: https://issues.apache.org/jira/browse/PIVOT-899
>             Project: Pivot
>          Issue Type: Bug
>            Reporter: Andrew Muldowney
>            Priority: Minor
>              Labels: faceting, limit, mincount, pivot
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> At defaults the facet.mincount = 0 while the facet.pivot.mincount = 1.
> Within the pivot facet code, a facet is made by calling "getTermCounts" which adheres to the facet.mincount and facet.limit. When sorting by index it is very possible for this call to return a whole bunch of results with a count of 0 before any count of 1 results showed up. The facet.limit can be set so that all the results from the "getTermCounts" call are below the facet.pivot.mincount, resulting in nothing being attached to the pivot facet result, which is clearly incorrect.
> In any situation where the facet.mincount is lower than the facet.pivot.mincount the results will be incorrect.

--
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