executions and couldn't reproduce slowdown.
Thanks for provided assistance,
Tomislav
2011/5/3 Michael McCandless :
> On Tue, May 3, 2011 at 7:43 AM, Tomislav Poljak wrote:
>> Hi,
>>
>> 2011/5/3 Michael McCandless :
>>> I feel like we are back to Basic ;)
>&g
t; From: Michael McCandless
>>> To: java-user@lucene.apache.org
>>> Sent: Mon, May 2, 2011 12:15:40 PM
>>> Subject: Re: MultiPhraseQuery slowing down over time in Lucene 3.1
>>>
>>> By "slowing down over time" do you mean you use the same ind
Hi,
after running tests on both MemoryIndex and RAMDirectory based index
in Lucene 3.1, seems MultiPhraseQueries are slowing down over time
(each iteration of executing the same MultiPhraseQueries on the same
doc, seems to require more and more execution time). Are there any
existing/known issues r
Hi,
when is it wise to replace a TermQuery with cached Filter (regarding
search performance). If TermQuery is used only to filter results based
on field value (it doesn't participate in scoring), is it alway wise to
replace it with filter? Is it only wise if Filter is cached (wrapped in
CachingWrap
Hi,
in API documentation for TermsFilter:
http://search-lucene.com/jd/lucene/org/apache/lucene/search/TermsFilter.html
it states:
'As a filter, this is much faster than the equivalent query (a
BooleanQuery with many "should" TermQueries)'
I would like to replace "should" TermQueries with TermsF
documents, how many fields and how many
> > numeric fields in which configuration do you use?
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
&
Hi,
is it normal for indexing time to increase up to 10 times after
introducing NumericField instead of Field (for two fields)?
I've changed two date fields from String representation (Field) to
NumericField, now it is:
doc.add(new NumericField("time").setIntValue(date.getTime()/24/3600))
and a
