Thanks for that Jack,
so it's fair to say that if both the sources and target corpus are large
and diverse, then the impact of using a different index to create the
query would be negligible.
P.
On 04/04/2013 06:49 PM, Jack Krupansky wrote:
The heart of MLT is examining the top result of
In a statistical sense, for the majority of documents, yes, but you could
probably find quite a few outlier examples where the results from A to B or
from B to A as significantly or even completely different or even
non-existent.
-- Jack Krupansky
-Original Message-
From: Peter
On Fri, Apr 5, 2013 at 4:05 AM, Wei Wang welshw...@gmail.com wrote:
Do we need to use setLongValue() all the time?
Yes.
--
Adrien
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands,
We are doing some crash resiliency testing of our application. One of the
things we found is that the Lucene index seems to get out of sync with the
database pretty easily. I suspect this is because we are using near real time
readers and never actually calling IndexWriter.commit(). I'm
Hi,
I've multiple fields (name, name2 - content copied below). And if I
extract the weighted span terms out based on a query (the query is with a
specific field) why am I not getting the positions properly out of the
WeightedSpanTerm covering multiple fields ?
Is it because the query is
