You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2010/01/08 20:17:54 UTC
[jira] Created: (SOLR-1712) option to supress facet constraints
when count is == numFound
option to supress facet constraints when count is == numFound
-------------------------------------------------------------
Key: SOLR-1712
URL: https://issues.apache.org/jira/browse/SOLR-1712
Project: Solr
Issue Type: Improvement
Reporter: Hoss Man
It would be handy to have an easy option to suppress (on the server side) any facet contraint values whose count is the same as numFound (ie: filtering on that constraint would not reduce the result size)
this should be a corollary to facet.mincount=1 and happen prior to facet.limit being applied.
http://old.nabble.com/Removing-facets-which-frequency-match-the-result-count-to27026359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1712) option to supress facet constraints
when count is == numFound
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798145#action_12798145 ]
Hoss Man commented on SOLR-1712:
--------------------------------
one idea for extending the functionality beyond a simple boolean...
"facet.maxcount" ... if it's a positive number, then any constraint who'se value is greater then facet.maxcount would be eliminated.
if facet.maxcount is a negative number, then it is subtracted from numFound, and the result is used as the maxcount.
* {{facet.maxcount=0}} (default) no upper limit on constraints returned
* {{facet.maxcount=100}} would only show contraints where filtering would reduce the result set to _no more then_ 100)
* {{facet.maxcount=-1}} would only show constraints where filtering would reduce the result set by at least 1
* {{facet.maxcount=-10}} would only show constraints where filtering would reduce the result set by at least 10
...once upon a time this would have been easy to implement in the basic faceting code, but i'm not even sure how to try and approach it with the distributed faceting code.
any suggetions?
> option to supress facet constraints when count is == numFound
> -------------------------------------------------------------
>
> Key: SOLR-1712
> URL: https://issues.apache.org/jira/browse/SOLR-1712
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> It would be handy to have an easy option to suppress (on the server side) any facet contraint values whose count is the same as numFound (ie: filtering on that constraint would not reduce the result size)
> this should be a corollary to facet.mincount=1 and happen prior to facet.limit being applied.
> http://old.nabble.com/Removing-facets-which-frequency-match-the-result-count-to27026359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1712) option to supress facet constraints
when count is == numFound
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798147#action_12798147 ]
Yonik Seeley commented on SOLR-1712:
------------------------------------
Also keep in mind that the docset used for faceting may not be the one used to return results (this is true for multi-select).
And yes, if you still want the top 10 constraints *after* eliminating those with count>=facet.maxcount, it makes distributed search *much* harder (and probably makes future per-segment faceting harder too).
> option to supress facet constraints when count is == numFound
> -------------------------------------------------------------
>
> Key: SOLR-1712
> URL: https://issues.apache.org/jira/browse/SOLR-1712
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> It would be handy to have an easy option to suppress (on the server side) any facet contraint values whose count is the same as numFound (ie: filtering on that constraint would not reduce the result size)
> this should be a corollary to facet.mincount=1 and happen prior to facet.limit being applied.
> http://old.nabble.com/Removing-facets-which-frequency-match-the-result-count-to27026359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.