It is usually best to cache the IndexSearcher across requests. If you have
to keep re-opening an IndexSearcher for each search you lose out on any
caching that Lucene can do. I usually just put it in the cache for x
minutes.
The IndexWriter works great with multiple threads. I usually have one
Ind
updating threads. Trying
>> to
>> > open the same index twice will throw exception. It is also recommended to
>> > share a single IndexSearcher across threads for better performance.
>> >
>> > DIGY
>> >
>> > -----Original Message-
&
earcher across threads for better performance.
> >
> > DIGY
> >
> > -Original Message-
> > From: Corey Trager [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, October 11, 2008 7:36 PM
> > To: lucene-net-user@incubator.apache.org
> > Subject:
ne-net-user@incubator.apache.org
> Subject: RE: Multiple threads updating/reading the same index in an
ASP.NET
> website. - IndexModifier
>
> Digg - thanks. I originally wrote this at StackOverflow.com. Do you think
I
> understand things
> now, based on what I wrote here:
>
&
ll, and leave it always open?
> >
> > Again for 2.3.1, IndexSearcher will not "see" the updates made by
> > IndexWriter unless you reopen it.
> >
> > DIGY
> >
> >
> > -Original Message-
> > From: Corey Trager [mailto:[EM
.org
Subject: RE: Multiple threads updating/reading the same index in an ASP.NET
website. - IndexModifier
Digg - thanks. I originally wrote this at StackOverflow.com. Do you think I
understand things
now, based on what I wrote here:
"After reading docs and experimentation, this is what I t
3.1, IndexSearcher will not "see" the updates made by
> IndexWriter unless you reopen it.
>
> DIGY
>
>
> -Original Message-----
> From: Corey Trager [mailto:[EMAIL PROTECTED]
> Sent: Sunday, October 12, 2008 12:52 AM
> To: lucene-net-user@incubator.apache.or
made by
IndexWriter unless you reopen it.
DIGY
-Original Message-
From: Corey Trager [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 12, 2008 12:52 AM
To: lucene-net-user@incubator.apache.org
Subject: RE: Multiple threads updating/reading the same index in an ASP.NET
website. - IndexM
iginal Message-
> From: Corey Trager [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 11, 2008 7:36 PM
> To: lucene-net-user@incubator.apache.org
> Subject: Multiple threads updating/reading the same index in an ASP.NET
> website.
>
> Does Lucene.Net have built into it logi
>
> DIGY
>
> -Original Message-
> From: Corey Trager [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 11, 2008 7:36 PM
> To: lucene-net-user@incubator.apache.org
> Subject: Multiple threads updating/reading the same index in an ASP.NET
> website.
>
&
share a single IndexSearcher across threads for better performance.
DIGY
-Original Message-
From: Corey Trager [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 11, 2008 7:36 PM
To: lucene-net-user@incubator.apache.org
Subject: Multiple threads updating/reading the same index in an
Does Lucene.Net have built into it logic for managing concurrency, multiple
threads? If a
request comes to my website that triggers a thread to update the index, and
another request comes
on another thread that also triggers a request to update, or even read, the
index, does Lucene
handle the
12 matches
Mail list logo
