[
https://issues.apache.org/jira/browse/LUCENE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-446.
Resolution: Fixed
committed (experimental mode).
> search.function - (1) score based on fi
Ord and ReverseOrd valueSource classes that are in use in Solr
- warn in the javadocs from the experimental state of this package
Javadocs were updated at http://people.apache.org/~doronc/api
I will commit this later today of there are no objections.
> search.function - (1) score based
this
package.
> search.function - (1) score based on field value, (2) simple score
> customizability
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira
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
useful?
Do you think they should be included?
Thanks,
Doron
> search.function - (1) score based on field value, (2) simple score
> customizability
> --
>
> Key: LUCENE-446
>
FieldScoreQuery to FieldScoreQuery.Type (e.g.
FieldScoreQuery.Type.BYTE).
- some documentation fixes.
Updated patch javadocs in http://people.apache.org/~doronc/api/
> search.function - (1) score based on field value, (2) simple score
> customiza
reviewed at http://people.apache.org/~doronc/api
> search.function - (1) score based on field value, (2) simple score
> customizability
> --
>
> Key: LUCENE-446
>
: (was: 1.9)
Fix Version/s: 2.2
Summary: search.function - (1) score based on field value, (2)
simple score customizability (was: FunctionQuery - score based on field value)
Modifying the issue name to reflect its current content.
> search.function - (1) score based
quite a few bugs for me, and I hope I got the scorers and
weight
correct now - I would very much appreciate review comments on these delicate
parts.,,
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
>
[
https://issues.apache.org/jira/browse/LUCENE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen reassigned LUCENE-446:
--
Assignee: Doron Cohen
> FunctionQuery - score based on field va
.)
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
> Issue Type: New Feature
>
ed at
FunctionQuery but didn't really see an easy way of getting around the
ValueSource thing.
See LUCENE-850 for my eventual solution
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL:
another query to get a multiplicative effect,
but is that the simplest approach?
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira/browse/LUCENE-446
>
ooked at it: i don't think FunctionQuery has any good unit tests in the Solr
code base -- there might be some tests that use the SOlrTestHarness to trigger
function queries, but they aren't really portable.
> FunctionQuery - score ba
ll be migrating to Lucene would you? :)
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
>
people want
this in Lucene.
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
> Is
ery - score based on field value
> --
>
> Key: LUCENE-446
> URL: https://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
> Issue Type: New Feature
> Compone
Lucene? I see
from time to time on java-user that it comes in handy for people using Lucene.
What do the Solr people think about moving it into Lucene core?
> FunctionQuery - score based on field value
> --
>
> Key
(linear(myfield,1.0,.1), 5.0)"
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: http://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
> Type: New Feat
ates the scoring to the functionquery it wraps, then applying an
additional function to it. Is that similar to the product function you mention?
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: http://is
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: function.zip
changed getSimpleName() to getName() to preserve Java1.4 compatability.
> FunctionQuery - score based on field va
;t done the "product" function yet... right now, the normal
way tocombine with other queries to influence the score is to put it in a
boolean query:
+other_lucene_query_clauses +function_query^.1
the score from the function query is added to the other query.
> FunctionQ
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: function.zip
attaching newest version
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: ReverseOrdFieldSource.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FunctionQuery.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: ReciprocalFloatFunction.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: OrdFieldSource.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: IntFieldSource.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: LinearFloatFunction.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FunctionInst.java)
> FunctionQuery - score based on field value
> --
>
> Key
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FunctionFactory.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FloatFieldSource.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FieldValueSourceFactory.java)
> FunctionQuery - score based on field value
> --
>
>
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: (was: FieldValueSource.java)
> FunctionQuery - score based on field value
> --
>
>
,
and ReverseOrdFieldSource, which numbers terms in reverse order as
OrdFieldSource
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: http://issues.apache.org/jira/browse/LUCENE-446
> Proj
package name suggestions/preferences?
search.fq?
search.func?
search.function?
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: http://issues.apache.org/jira/browse/LUCENE-446
> Proj
: org.apache.lucene.search.fq
> FunctionQuery - score based on field value
> --
>
> Key: LUCENE-446
> URL: http://issues.apache.org/jira/browse/LUCENE-446
> Project: Lucene - Java
> Type: New Feature
> Components: Se
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: FloatFieldSource.java
IntFieldSource.java
OrdFieldSource.java
> FunctionQuery - score based on field va
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: FunctionInst.java
FieldValueSourceFactory.java
FieldValueSource.java
> FunctionQuery - score based on field va
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: FunctionQuery.java
LinearFloatFunction.java
FunctionFactory.java
> FunctionQuery - score based on field va
FunctionQuery - score based on field value
--
Key: LUCENE-446
URL: http://issues.apache.org/jira/browse/LUCENE-446
Project: Lucene - Java
Type: New Feature
Components: Search
Versions: 1.9
Reporter: Yonik
Here is another prototype.
Field value retrieval has been decoupled from function calculation, so one
will be able to use a field of any type with the same function class.
Comments?
If not, I think this may be the version I clean up, implement sources for
Integer and Ordinal fields, and submit to
There has been a lot of interest in generating a score or boosting based on
the value of a particular field.
Here is my first prototype that can handle int and float field values.
I'm not particularly happy with the form of this solution yet, which is why
I'm throwing it out to dev to see if anyone
43 matches
Mail list logo
