[
https://issues.apache.org/jira/browse/LUCENE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved LUCENE-5598.
------------------------------------
Resolution: Not a Problem
Please raise usage questions on the user's list rather than raising a JIRA. The
JIRA is for know bugs/code changes and this is neither.
See: https://lucene.apache.org/solr/discussion.html
Best,
Erick
> About Scoring
> -------------
>
> Key: LUCENE-5598
> URL: https://issues.apache.org/jira/browse/LUCENE-5598
> Project: Lucene - Core
> Issue Type: Wish
> Components: core/query/scoring
> Affects Versions: 4.7
> Reporter: Park JungHo
> Labels: mentor, patch
> Fix For: 4.7
>
>
> I had been generating long type's indexing data using LongField(Field name is
> 'boost' and value is atomicLong.) for using CustomScoreQuery.
> And then, I'm applied following code.
>
> //code start ========================================
> FunctionQuery fquery = new FunctionQuery(new LongFieldSource("boost"));
> CustomScoreQuery customQuery = new ScoreQuery(query, fquery);
> //code end =========================================
>
> If indexed data count is 100, I expect 100, 99, 98, ... 91.
> But, the result was not matched with my expectation if the number of the
> indexed data gets increased. (For instance 999999985, 999999986, 999999987,
> 999999988, ... 999999994 when one billion index count )
>
> I thought that was caused by scoring alogorithm returning float value.
> (Floating point limit.)
> That is correct?
> How can I get the result i expect?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
