I've created https://issues.apache.org/jira/browse/LUCENE-3442 to document this.
Thanks for your help,
Dan
- Original Message -
From: Uwe Schindler
To: [email protected]
Cc:
Sent: Tuesday, September 20, 2011 11:01 AM
Subject: RE: QueryWrapperFilter and DocIdSetIterat
assumption.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]
> -Original Message-
> From: Uwe Schindler [mailto:[email protected]]
> Sent: Tuesday, September 20, 2011 7:33 PM
> To: [email protected]; aberdee...@y
Hi,
I don't see a problem in your code:
If you look at the source code of QueryWrapperFilter, it will never return
NULL, so it returns always a DocIdSet theat itself returns the Scorer of the
query as Iterator.
@Override
public DocIdSet getDocIdSet(final IndexReader reader) throws IOException
My first bit of advice would be to step back and take a deep
breath and "take off your DB hat". Lucene is a *text* search
application, not an RDBMS.
The usual solution is to flatten your data representation when
you index so you can use simpler searches. Others have
posted that it's hard to use Lu
What version of Lucene are you using? Can you share the snippet of
code that does this? Are you keeping the QueryWrapperFilter around
from search to search?
On Jun 27, 2008, at 5:24 PM, Jordon Saardchit wrote:
Hello All,
Sort of new to lucene but have a general question in regards to
pe
Op Thursday 17 April 2008 06:37:18 schreef Michael Stoppelman:
> Actually, I screwed up the timing info. I wasn't including the time
> for the QueryWrapperFilter#bits(IndexReader) call. Sadly,
> it actually takes longer than the original query that had both terms
> included. Bummer. I had really co
Actually, I screwed up the timing info. I wasn't including the time for the
QueryWrapperFilter#bits(IndexReader) call. Sadly,
it actually takes longer than the original query that had both terms
included. Bummer. I had really convinced myself till the
thought came to me at lunch :).
-M
On Wed, A
Michael Stoppelman skrev:
Hi all,
I've been doing some performance testing and found that using
QueryWrapperFilter for a location field
restriction I have to do allows my search results to approach 5-10ms. This
was surprising.
Before the performance was between 50ms-100ms.
The queries from befor
