java-user@lucene.apache.org
[Top] [All Lists]

Re: QueryParser not thread-safe

Subject: Re: QueryParser not thread-safe
From: jian chen
Date: Tue, 23 Aug 2005 12:38:02 -0700
Right. My philosophy is that, make it work, then, make it better. 

Don't waste time on something that you are not sure if it would cause
performance problem.

Jian

On 8/23/05, Paul Elschot <paul.elschot@xxxxxxxxx> wrote:
> On Tuesday 23 August 2005 19:01, Miles Barr wrote:
> > On Tue, 2005-08-23 at 13:47 -0300, jhandl@xxxxxxxxxxxxxxx wrote:
> > > Hi! I've been having problems with lucene's QueryParser, apparently it is
> not thread-safe.
> > >
> > > That means I can't parse queries in threads where the queryparser object
> is created once and reused for each query. If I do, the resulting queries may
> have all kinds of weird problems, for example missing terms, duplicate terms,
> etc.
> > >
> > > I don't like the idea of creating a new queryparser for each query, so I
> am looking for alternatives. Any ideas?
> >
> > Using a non-threadsafe object in a threaded environment is fairly
> > standard in Java, just wrap it in a synchronized block.
> >
> > If you don't want all threads waiting on one query parser, create a pool
> > of them.
> 
> Or use one parser per thread.
> 
> Regards,
> Paul Elschot
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: java-user-help@xxxxxxxxxxxxxxxxx
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: java-user-help@xxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>