Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Subject: Re: QueryParser not thread-safe
From: Miles Barr <miles@runtime-collective.com>
To: java-user@lucene.apache.org
In-Reply-To: <f4c78503c21c.430b28ea@fibertel.com.ar>
References: <f4c78503c21c.430b28ea@fibertel.com.ar>
Content-Type: text/plain
Organization: Runtime Collective Ltd.
Date: Tue, 23 Aug 2005 18:01:29 +0100
Message-Id: <1124816490.11257.81.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2005-08-23 at 13:47 -0300, jhandl@fibertel.com.ar 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. 


-- 
Miles Barr <miles@runtime-collective.com>
Runtime Collective Ltd.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org