[
https://issues.apache.org/jira/browse/LUCENE-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304054#comment-16304054
]
Robert Muir commented on LUCENE-8087:
-------------------------------------
Well its not just similarity-specific information right? Thats annoying in
itself, I think its wrong to have to reindex to change a bm25 parameter. But
its more than that, It'd have the same challenges as LUCENE-4100:
incompatibility with distributed search and incorrect with incremental
indexing, except for TFxIDF-type equations where term/collection statistics can
be easily factored out.
> Record per-term max term frequencies
> ------------------------------------
>
> Key: LUCENE-8087
> URL: https://issues.apache.org/jira/browse/LUCENE-8087
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-8087.patch
>
>
> I was mostly interested in doing that in order to get better score upper
> bounds for LUCENE-4100. However this doesn't help, at least with the tasks
> that we have for wikimedium10m. I dug this a bit, and this is due to the fact
> that the upper bound is not much better if we can't make assumptions about
> the value of the length. Ideally we'd need something like the maximum term
> frequency for each norm value. I'll post the patch in case someone has
> another use-case for per-term max term frequencies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
