[
https://issues.apache.org/jira/browse/LUCENE-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269260#comment-16269260
]
Hoss Man commented on LUCENE-8069:
----------------------------------
bq. Sorry I wasn't clear but this is what I meant indeed (norms store the field
length as of 7.0).
Hmmm... that's how the default sim works as of 7.0, but strictly speaking a
custom Similarity class could still do anything it wants in computeNorm() ...
correct?
I'm not trying to split hairs, i just want to clarify that in terms of the
implementation details you're suggesting "sort by (long) norm value
(ascending)" and in terms of naming/documenting this feature it should be clear
that's what it will-do -- that if a user configures some weird sim that
computes a weird norm they're not going to get "sort by doc length" they're
going to get "sort by your weird norm"
> Allow index sorting by field length
> -----------------------------------
>
> Key: LUCENE-8069
> URL: https://issues.apache.org/jira/browse/LUCENE-8069
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Adrien Grand
> Priority: Minor
>
> Short documents are more likely to get higher scores, so sorting an index by
> field length would mean we would be likely to collect best matches first.
> Depending on the similarity implementation, this might even allow to early
> terminate collection of top documents on term queries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
