ginal Message-
> From: Alan Woodward [mailto:a...@flax.co.uk]
> Sent: Montag, 8. Juni 2015 12:23
> To: java-user@lucene.apache.org
> Subject: Re: Memory problem with TermQuery
>
> Hi Anna,
>
> In normal usage, perReaderTermState will be null, and TermQuery will be very
&g
@lucene.apache.org
Subject: Re: Memory problem with TermQuery
Hi Anna,
In normal usage, perReaderTermState will be null, and TermQuery will be very
lightweight. It's in particular expert use cases (generally after queries have
been rewritten against a specific IndexReader) that the perReaderTermState wil
itten queries somehow?
Alan Woodward
www.flax.co.uk
On 8 Jun 2015, at 10:49, Anna Maier wrote:
> Hi,
>
> we ran into a memory problem with TermQuery: in our program, we build a
> TermQuery object from the user input and pass it around, to be able to
> different things, like execute
Hi,
we ran into a memory problem with TermQuery: in our program, we build a
TermQuery object from the user input and pass it around, to be able to
different things, like execute the query again and so on. So, the TermQuery
object can potentially exist for some time.
Now it turns out, that a
