We've decided in 1575 to pre-populate HitQueue with sentinel values with
score = Float.NEG_INF, as we assumed these scores will not be produced. TSDC
instantiates HitQueue with pre-filling turned on.
Is NEG_INF a valid score for you?
On Tue, May 26, 2009 at 4:48 PM, Yonik Seeley <yo...@lucidimagination.com>wrote:
> I'm attempting to switch Solr to use the new Collector framework to
> get per-segment sorting and have been hitting some issues.
> The latest is a function query log(val) which produces both NaN and
> -Infinity values, which kill the TopScoreDocCollector (invalid docids
> are produced).
>
> results = {org.apache.lucene.search.scoredoc...@2039}
> [0] = {org.apache.lucene.search.score...@2042}"doc=0 score=2.0"
> [1] = {org.apache.lucene.search.score...@2043}"doc=4 score=1.39794"
> [2] = {org.apache.lucene.search.score...@2044}"doc=3 score=1.0"
> [3] = {org.apache.lucene.search.score...@2045}"doc=5 score=0.69897"
> [4] = {org.apache.lucene.search.score...@2046}"doc=1 score=-2000000.0"
> [5] = {org.apache.lucene.search.score...@2047}"doc=2147483647
> score=-Infinity"
> [6] = {org.apache.lucene.search.score...@2048}"doc=2147483647
> score=-Infinity"
>
> So either we need to clarify the valid values for score() or we need
> to change how the queue does comparisons so that this works again.
>
> -Yonik
> http://www.lucidimagination.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-dev-h...@lucene.apache.org
>
>
