: OK this could make sense (floating point math is frustrating!).
:
: But, Lucene generally scores one document at a time, so in theory just
: changing its docid shouldn't alter the order of float operations.
i haven't thought this through, but couldn't scorer re-ordering in
BooleanScorer2 poss
On Wed, Apr 4, 2012 at 4:18 PM, Michael McCandless
wrote:
> On Wed, Apr 4, 2012 at 6:15 PM, Alan Bawden wrote:
>> The key observation is that the differences in scores we see are always
>> down around the sixth decimal place -- down where 32-bit floating point
>> loses precision.
>8 snip 8<-
On Wed, Apr 4, 2012 at 6:15 PM, Alan Bawden wrote:
> So I sat down to try to make a small test case that exhibited this
> behavior, and while I was working on that I thought of a possible
> explanation for what we are seeing. If you agree that my explanation is
> what's going on here, then Benson
So I sat down to try to make a small test case that exhibited this
behavior, and while I was working on that I thought of a possible
explanation for what we are seeing. If you agree that my explanation is
what's going on here, then Benson and I can stop working on making a test
case, and move on t
hello! http://downloads.supportandmore.de/amrv-10-11.html?jhID=8aus2
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
Using the original org.apache.lucene.search.highlight.Highlighter should I be
able to give it a query like [ My AND Words AND "My Words"^100 ] (the actually
phrase in this query is converted to a span query with a slop 1),
and expect it find the fragment many pages into the file that has span "My
Hi Martijn,
Thank you for responding so quickly. I found my reply was stuck in my drafts
folder so apologies for not getting back sooner. I'm trying to search and join
across two disparate document types that have some common features. Your
response confirms what I was looking into.
My unders