lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-1656) When sorting by field, IndexSearcher should not compute scores by default
Date Wed, 27 May 2009 15:02:45 GMT


Shai Erera commented on LUCENE-1656:

Maybe state in CHANGES that IndexSearcher.setDefaultFieldSortScoring is deprecated and it
is just an intermediary solution? In 3.0, the only way to achieve that will be creating TFC

Also, the tests call this method and set it to true. Since this new method is deprecated,
we'll need to change those tests again in 3.0. Can they create TFC instead and call the appropriate
search method?

> When sorting by field, IndexSearcher should not compute scores by default
> -------------------------------------------------------------------------
>                 Key: LUCENE-1656
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1656.patch
> In 2.9 we've added the ability to turn off scoring (maxScore &
> trackScores, separately) when sorting by field.
> I expect most apps don't use the scores when sorting by field, and
> there's a sizable performance gain when scoring is off, so I think for
> 2.9 we should not score by default, and add show in CHANGES how to
> enable scoring if you rely on it.
> If there are no objections, I'll commit that change in a day or two
> (it's trivial).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message