Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <09c301d33880$ab8ed3f0$02ac7bd0$@thetaphi.de>
References: <CAA4R6b8j9tKQMS7XmW6P7StipF5FW2qkLhVfMKKw=Av8WXKuig@mail.gmail.com>
 <09c301d33880$ab8ed3f0$02ac7bd0$@thetaphi.de>
From: Yonghui Zhao <zhaoyonghui@gmail.com>
Date: Fri, 29 Sep 2017 11:17:09 +0800
Message-ID: <CAA4R6b8LPJMTV5Je2LFOGWzJCea+cKH-iYwP=dAcScP2FDH=0w@mail.gmail.com>
Subject: Re: TieredMergePolicy disrupts doc id order after merge
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary="001a11405e92d8b1be055a4b7503"
archived-at: Fri, 29 Sep 2017 03:17:22 -0000

--001a11405e92d8b1be055a4b7503
Content-Type: text/plain; charset="UTF-8"

Got it, thanks Uwe!

2017-09-29 1:39 GMT+08:00 Uwe Schindler <uwe@thetaphi.de>:

> Hi,
>
> Use another merge policy, see LogMergePolicy subclasses! Those preserve
> order, but are not merging in ideal ways.
>
> In general: Relying on internal Lucene DocIDs is not guaranteed to work,
> this is only an implementation detail. The internal IDs are also not
> stable!!!
>
> Uwe
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> > -----Original Message-----
> > From: Yonghui Zhao [mailto:zhaoyonghui@gmail.com]
> > Sent: Thursday, September 28, 2017 2:50 PM
> > To: java-user@lucene.apache.org
> > Subject: TieredMergePolicy disrupts doc id order after merge
> >
> > Hi,
> >
> > It is easier to elaborate my question  with an example.
> >
> > My lucene version is 4.10.4
> >
> > I use
> >
> > SortField sortField =  new SortField(null, SortField.Type.DOC, true);
> > sort = new Sort(sortField);
> > return new SortingMergePolicy(new TieredMergePolicy(), sort);
> >
> >
> > to make sure my index merger will make fresh documents in the beginning
> of
> > merged segment.
> >
> > TieredMergePolicy will chose biggest segments to merge, so the merge
> order
> > should be size descending order.
> >
> > Say we have 2 segments, segment 0 size is smaller than segment 1, after
> > size sorting merge readers are (segment 1, segment 0),   after merge all
> > docs in segment 1 are  in front of segment 0.
> >
> > This doesn't satisfy my requirement.
> >
> > If merge readers will be restored to origin order after TieredMergePolicy
> > findMerges, then this problem will be fixed.
> >
> > Any problem of this solution?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--001a11405e92d8b1be055a4b7503--