Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAPzrt-2+957iTiD5ZMCH+sBy3WSEE3ax2J6C6pT6vEV3hiGvOw@mail.gmail.com>
References: 
 <CAPzrt-2+957iTiD5ZMCH+sBy3WSEE3ax2J6C6pT6vEV3hiGvOw@mail.gmail.com>
From: Michael McCandless <lucene@mikemccandless.com>
Date: Sat, 4 Jan 2014 05:23:31 -0500
Message-ID: 
 <CAL8PwkYfnMygiXC5hnMbLK4rW455NHbBoj4iGzxgG6vOeus-Fg@mail.gmail.com>
Subject: Re: TieredMergePolicy and Doc ordering
To: Lucene Users <java-user@lucene.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Lucene's internal docIDs will change their order, but often this
doesn't matter and you won't see it.

E.g. if you search and you're sorting by your ID field then Lucene's
docID assignments has no effect.

It's only for tie-breaks where Lucene falls back to its docID to break the tie.

Mike McCandless

http://blog.mikemccandless.com


On Fri, Jan 3, 2014 at 5:16 AM, Ramprakash Ramamoorthy
<youngestachiever@gmail.com> wrote:
> Team,
>
> I'm using Lucene 4.4 and am indexing my documents using TieredMergePolicy.
> The documents I index have an incremental ID field. From the javadoc, I see
> that, tiered merge policy merges non adjacent segments.
>
> However, when I try to search through in my test environment, I get the
> search results in perfect order of incremental IDs. In case non adjacent
> segments are merged, then there should be a change in order of the IDs
> right? Or am I missing something?
>
>
>
> --
> With Thanks and Regards,
> Ramprakash Ramamoorthy,
> Chennai, India.

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