[
https://issues.apache.org/jira/browse/SOLR-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621671#action_12621671
]
Mark Miller commented on SOLR-517:
----------------------------------
Yeah, I had tried to turn that test into duplicate Lucene actions, and I
couldn't replicate the problem. I will give it a whirl with solr when I get a
chance.
What values for totalNumDocs and docFreq are being used when you get the
exception? I still don't see how your seeing a negative there...
>>I'm afraid but I don't understand what you are saying (current trunk is using
>>IndexReader method).
If you use the IndexReader method token scoring is done using the idf formula -
so you could do highlighting to varying degrees based on the score. There is a
cost to this to get the info for the idf calculation and then also the
calculation. If you don't use the IndexReader method, hits are just scored 1 or
0 pretty much. Thats all thats need for basic highlighting. But if no one is
using the richer highlighting scores, you pay for nothing.
> highlighter doesn't work with hl.requireFieldMatch=true on un-optimized index
> -----------------------------------------------------------------------------
>
> Key: SOLR-517
> URL: https://issues.apache.org/jira/browse/SOLR-517
> Project: Solr
> Issue Type: Bug
> Components: highlighter
> Affects Versions: 1.2, 1.3
> Reporter: Koji Sekiguchi
> Priority: Minor
> Attachments: SOLR-517.patch, SOLR-517.patch, SOLR-517.patch
>
>
> On un-optimized index, highlighter doesn't work with
> hl.requireFieldMatch=true.
> see:
> http://www.nabble.com/hl.requireFieldMatch-and-idf-td16324482.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
