You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Kay Kay (JIRA)" <ji...@apache.org> on 2009/02/23 16:22:02 UTC
[jira] Commented: (SOLR-1019) ConstantScorePrefixQuery.java -
Absolute FP comparison on getBoost()
[ https://issues.apache.org/jira/browse/SOLR-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675945#action_12675945 ]
Kay Kay commented on SOLR-1019:
-------------------------------
I believe either of the scenarios in which the fix might be invalid would be related to the value of epsilon . If we keep the value of epsilon small enough - Math.Double.MIN_VALUE - we might get around the issue. The bottom line is that absolute FP comparisons can result in unpredictable behaviors, depending on the underlying implementation something that we want to avoid.
> ConstantScorePrefixQuery.java - Absolute FP comparison on getBoost()
> ---------------------------------------------------------------------
>
> Key: SOLR-1019
> URL: https://issues.apache.org/jira/browse/SOLR-1019
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 1.3
> Environment: Java 6, Tomcat 6
> Reporter: Kay Kay
> Attachments: SOLR-1019.patch
>
>
> Absolute FP comparisons are inherently unsafe. Comparisons of FP done under an epsilon resolution difference.
> affects ConstantScorePrefixQuery#toString() and #equals()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.