After some more research, it seems that one of the bottlenecks is
Spans.next(), can I drop anything out in order to improve performance?
Most of the queries are SpanNearQuery with SpanOrQuery as its clauses.
Any help would be much appreciated.
Regards,
Michael
On 5/25/06, Michael Chan <[EMAIL
I see.
Also, as I'm only interested in the number of results returned and not
in the ranking of documents returned, is there any component I can
simplify in order to improve search performance? Perhaps, Scorer or
Similarity?
Thanks.
Michael
On 5/24/06, Chris Hostetter <[EMAIL PROTECTED]> wrote
: Unfortunately, I want to have subqueries inside my query (e.g. (t1 AND
: t2) NEAR (t3 OR t4)), and PhraseQuery seems to allow only Terms inside
: it.
In that case, you aren't just using SpanQuery for the use of slop -- you
are using the Span information, you just don't realize it (that's how al
Hi Erik,
Unfortunately, I want to have subqueries inside my query (e.g. (t1 AND
t2) NEAR (t3 OR t4)), and PhraseQuery seems to allow only Terms inside
it.
Michael
On 5/23/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
PhraseQuery has a slop factor also - would it work for you instead of
SpanNearQ
PhraseQuery has a slop factor also - would it work for you instead of
SpanNearQuery?
Erik
On May 23, 2006, at 1:36 AM, Michael Chan wrote:
Hi,
As I use SpanQuery purely for the use of slop, I was wondering how to
make SpanQuery more efficient,. Since I don't need any span
informatio
Hi,
As I use SpanQuery purely for the use of slop, I was wondering how to
make SpanQuery more efficient,. Since I don't need any span
information, is there a way to disable the computation for span and
other unneeded overhead?
Thanks.
Michael
---
