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

Yonik Seeley commented on LUCENE-4828:
--------------------------------------

bq. > For highlighting, I've heard it argued both ways (i.e. prohibited terms 
can be important too).
bq. Hmm can you give an example where it's useful to highlight the prohibited 
terms?

It wasn't my argument, but I guess it was along the lines that there can be 
info/relevance in the fact that the user did not want documents with a specific 
term, and thus it can make sense to highlight them (maybe with a diff color...)

bq. > I wasn't thinking about highlighting as much as something like 
distributed IDF or other global term statistics.
bq. But, normally, prohibited clauses don't contribute to scoring so the stats 
of terms inside them don't need to be distributed?

The key word there is "normally".  As I said, it depends on the type of query 
in the prohibited clause, and the boolean query does not have the knowledge to 
know if it will matter or not.  Something other than extractTerms could be used 
for distributed term stats though.


                
> BooleanQuery.extractTerms should not recurse into MUST_NOT clauses
> ------------------------------------------------------------------
>
>                 Key: LUCENE-4828
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4828
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 5.0, 4.3
>
>         Attachments: LUCENE-4828.patch
>
>


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