lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jacky <jackych...@gmail.com>
Subject Re: IndexSearcher executed concurrently
Date Tue, 05 Sep 2006 13:07:15 GMT
     Oh, that is great! I didn't notice this javadoc. Maybe  i need to
update my lucene lib.
     I had thought  one user requests his query, other queries maybe impact
on the result since using a single IndexSearcher.  Forget these mails.
Thanks a lot..



On 9/5/06, karl wettin <karl.wettin@gmail.com> wrote:
>
> On Tue, 2006-09-05 at 17:57 +0800, jacky wrote:
> > 1. I wander if concurrent users can get the right results with
> > different queries since the class has only one IndexSearcher instance.
> >
> > 2. As we know, a new IndexSearcher can be created when user request
> > his query. If first method gets the right result, so, which method can
> > get better performance.
>
> I'm afraid I don't understand your questions. What do you mean by "the
> right results"? Perhaps this quote from the javadocs is what you are
> looking for: For performance reasons it is recommended to open only one
> IndexSearcher and use it for all of your searches.
>
>
> http://lucene.apache.org/java/docs/api/org/apache/lucene/search/IndexSearcher.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>


-- 
  Best Regards.
      jacky

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message