Hi Christian,
I found an entry about this in the 4.0-ALPHA “Changes in backwards
compatibility policy” section of Lucene’s CHANGES.txt (html version):
<http://lucene.apache.org/core/4_9_0/changes/Changes.html#v4.0.0-alpha.changes_in_backwards_compatibility_policy>:
LUCENE-3514: IndexSearcher.setDefaultFieldSortScoring was removed
and replaced with per-search control via new expert search methods
that take two booleans indicating whether hit scores and max score
should be computed. (Mike McCandless)
See:
<http://lucene.apache.org/core/4_9_0/core/org/apache/lucene/search/IndexSearcher.html#search(org.apache.lucene.search.Query,%20org.apache.lucene.search.Filter,%20int,%20org.apache.lucene.search.Sort,%20boolean,%20boolean)>
Steve
On Jul 18, 2014, at 10:17 AM, Christian Reuschling <[email protected]>
wrote:
> We currently migrate one project to Lucene 4 and noticed that the method
> IndexSearcher.setDefaultFieldSortScoring(..) disappeared in Lucene 4.0. We
> can't find something
> about this in the migration guide. Further, it was never deprecated in Lucene
> 3, so we didn't find
> related documentation on it. Also didn't find something in the mailing list.
>
> Is it save to just leave it out? We use and display scores also if the result
> list was sorted by
> field value, so we set the field sort scoring to true in any case in the
> past. How can we achieve
> this now?
>
>
> best
>
> Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
