look into
NearSpansOrdered here might be a bit faster than the NearSpans
However what significantly slows us down is the hits.id(i) function.
Can we accelerate it somehow "cleaning" Lucene code itself from
scoring?
Best regards
Boris
On Thursday 11 May 2006 22:42, Boris Gali
Hello
We don't need any scoring in our application domain, but
efficiency is the key because we are getting tens thousand of hits for
span queries; all these hits are necessary to collect.
Is there a simple way to turn scoring off while indexing, while
search and while delivering docume
Hello
I am having problems running span queries with more than one
negative clauses:
Is the span query nested correctly?
spanNear([spanOr([contents:10.1.1.95, contents:10.1.1.81]),
spanNot(spanNear([contents:translated], 5000, false),
//posit
Hello
We need to construct nested span queries, and it seems like SrndQuery
is a good way to do it.
Are there examples available for SrndQueries? How to construct them
(is it using QueryParser?).
Where to get Surround Parser?
How to run them?
Best regards
Boris
-
I fully understand now. Thanks a lot
Boris
On Tue, 18 Apr 2006 11:10:20 -0700 (PDT)
Chris Hostetter <[EMAIL PROTECTED]> wrote:
: The question is when I get Spans, I get start/end positions and a
: Document order (starting from 0), not the Document object itself
from
Are you sure about that?
Thanks a lot Hoss
The question is when I get Spans, I get start/end positions and a
Document order (starting from 0), not the Document object itself from
which I could get a filename. Since I believe there is no way to get a
Document object from Spans, and there is no such thing as Document ID
Hello
I am using span queries to get hits (Documents) and occurrences
(positions) of search terms within these documents.
For some reason, there is a disagreement between the order the
Documents are returned in hits, and the Documents are referenced (via
order number, starting from 0) in
