lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-446) search.function - (1) score based on field value, (2) simple score customizability
Date Mon, 04 Jun 2007 02:38:15 GMT


Hoss Man commented on LUCENE-446:

Doron: I haven't really been able to keep up with the way this issue has evolved, or dig into
your new patches, but to answer your question about the Ord functions: yes they are very useful,
and it active use in Solr.  I believe the warning about MultiSearcher mainly has to do with
the fact that the MultiSearcher/FieldCache APIs give us know way to know the "lowest" of "highest"
value in a field cache across an entire logical index, so the Ord functions can't really be
queried against a MultiSearcher.

> search.function - (1) score based on field value, (2) simple score customizability
> ----------------------------------------------------------------------------------
>                 Key: LUCENE-446
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Search
>            Reporter: Yonik Seeley
>            Assignee: Doron Cohen
>            Priority: Minor
>             Fix For: 2.2
>         Attachments: function.patch.txt, function.patch.txt,,
> FunctionQuery can return a score based on a field's value or on it's ordinal value.
> FunctionFactory subclasses define the details of the function.  There is currently a
LinearFloatFunction (a line specified by slope and intercept).
> Field values are typically obtained from FieldValueSourceFactory.  Implementations include
FloatFieldSource, IntFieldSource, and OrdFieldSource.

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