[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282129#comment-13282129
]
Koji Sekiguchi commented on LUCENE-3440:
----------------------------------------
bq. Koji, do you wanna get this in any time? Now is likely a good time since
4.0 is getting close.
Hi Simon, thank you for bring this up to me! Yes, I do want sebastian's great
patch to get in 4.0. It has been on my TODO list for a long time, but I
couldn't find time to look into it deeply. I'm very sorry about that.
If I remember correctly, when I tried previous patch, I got errors on testing.
Then sebastian fixed them and attached updated patch. I looked into the updated
test, but I think I couldn't understand them very well at that time. Just after
that, couldn't have my time because I was assigned something.
Anyway, the idea of this ticket is definitely great and should be committed. So
can someone take over it?
> FastVectorHighlighter: IDF-weighted terms for ordered fragments
> ----------------------------------------------------------------
>
> Key: LUCENE-3440
> URL: https://issues.apache.org/jira/browse/LUCENE-3440
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/highlighter
> Reporter: sebastian L.
> Priority: Minor
> Labels: FastVectorHighlighter
> Fix For: 4.0
>
> Attachments: LUCENE-3440.patch, LUCENE-3440.patch,
> LUCENE-3440_3.6.1-SNAPSHOT.patch, LUCENE-4.0-SNAPSHOT-3440-9.patch,
> weight-vs-boost_table01.html, weight-vs-boost_table02.html
>
>
> The FastVectorHighlighter uses for every term found in a fragment an equal
> weight, which causes a higher ranking for fragments with a high number of
> words or, in the worst case, a high number of very common words than
> fragments that contains *all* of the terms used in the original query.
> This patch provides ordered fragments with IDF-weighted terms:
> total weight = total weight + IDF for unique term per fragment * boost of
> query;
> The ranking-formula should be the same, or at least similar, to that one used
> in org.apache.lucene.search.highlight.QueryTermScorer.
> The patch is simple, but it works for us.
> Some ideas:
> - A better approach would be moving the whole fragments-scoring into a
> separate class.
> - Switch scoring via parameter
> - Exact phrases should be given a even better score, regardless if a
> phrase-query was executed or not
> - edismax/dismax-parameters pf, ps and pf^boost should be observed and
> corresponding fragments should be ranked higher
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
