I use the code below to do something like this. Not exactly what you
want but should be easy to adapt.
public List findTerms(IndexReader _reader,
String _field) throws IOException {
List l = new ArrayList();
Fields ff = MultiFields.getFields(_reader);
Terms tr
Is this OOM happening as part of your early morning optimize or at
some other point? By optimize do you mean IndexWriter.forceMerge(1)?
You really shouldn't have to use that. If the index grows forever
without it then something else is going on which you might wish to
report separately.
--
Ian.
Yes, it happens as part of the early morning optimize, and yes, it's a
forceMerge(1) which I've disabled for now.
I haven't looked at the persistence mechanism for Lucene since 2.x, but
if I remember correctly, the deleted documents would stay in an index
segment until that segment was eventua
Hi,
TieredMergePolicy, which is the default since around Lucene 3.2, prefers
merging segments with many deletions, so forceMerge(1) is not needed.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From:
Thanks for clarifying Uwe. I will keep the daily optimization turned
off. I may be wrong, but I would guess that if the OOM is happening as
part of the forceMerge, then there may be a chance that it could also
happen as a natural part of the index growth when big segments are
merged. If so,
A quick update:
In order to confirm that none of the standard migration changes had a
negative effect on performance, I ported my Lucene 4.x version back to
Lucene 3.6.2 and kept the newer API rather than using the custom
ParallelMultiSearcher and other deprecated methods/classes.
Performance in
Thanks Mike. Yeah, I guess it wouldn't work for us in that case.
Marcos
On Mon, Sep 23, 2013 at 6:00 AM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Fri, Sep 20, 2013 at 11:59 AM, Marcos Juarez Lopez
> wrote:
>
> > Thanks for your quick response Mike. I'll be sure to pay mor
Hi Lan,
Thanks for your Reply.
I am doing similar to this only..In MultiPhraseQuery object actual phrase
is going proper but it is not returning any hits..
In Lucene 3.6,I implemented the same logic and it is working.
In Lucene 4.3,I implemented the Index for that using
FieldType offsetsType
