Re: Is RangeQuery more efficient than DateFilter?

2004-03-29 Thread Erik Hatcher
On Mar 29, 2004, at 4:25 AM, Kevin A. Burton wrote: I have a 7G index. A query for a random term comes back fast (300ms) when I'm not using a DateFilter but when I add the DateFilter it takes 2.6 seconds. Way too long. I assume this is because the filter API does a post process so it has to

Re: Is RangeQuery more efficient than DateFilter?

2004-03-29 Thread Erik Hatcher
On Mar 29, 2004, at 8:41 AM, Erik Hatcher wrote: On Mar 29, 2004, at 4:25 AM, Kevin A. Burton wrote: I have a 7G index. A query for a random term comes back fast (300ms) when I'm not using a DateFilter but when I add the DateFilter it takes 2.6 seconds. Way too long. I assume this is because

Re: Is RangeQuery more efficient than DateFilter?

2004-03-29 Thread Kevin A. Burton
Erik Hatcher wrote: One more point... caching is done by the IndexReader used for the search, so you will need to keep that instance (i.e. the IndexSearcher) around to benefit from the caching. Great... Damn... looked at the source of CachingWrapperFilter and it makes sense. Thanks for the

Re: Is RangeQuery more efficient than DateFilter?

2004-03-29 Thread Stephane James Vaucher
I've added some information contained on this thread on the wiki. http://wiki.apache.org/jakarta-lucene/DateRangeQueries If you wish to add more information, go right ahead, but since I added this info, I believe it's ultimately my responsibility to maintain it. sv On Mon, 29 Mar 2004, Kevin