Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 18591 invoked from network); 30 Jun 2010 03:13:41 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Jun 2010 03:13:41 -0000 Received: (qmail 55010 invoked by uid 500); 30 Jun 2010 03:13:39 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 54484 invoked by uid 500); 30 Jun 2010 03:13:36 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 54473 invoked by uid 99); 30 Jun 2010 03:13:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 03:13:36 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mail.apoorv@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-iw0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 03:13:28 +0000 Received: by iwn39 with SMTP id 39so235968iwn.35 for ; Tue, 29 Jun 2010 20:13:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=NYBZVjEAHTL554Q6ZhwkJNe1Lbapkb+xfn4/5N5G2BQ=; b=C/czRctI42dcHxY1Rouahl5pWFKGBwKIydGnv901JjFd76p9wOLNKq0YD2TmBijmPP g+dR6EQdoIQPFHCqqD1q540N+NX/fphdgr7obAcHPDKvOAqVvLIi4HAK3XblJWjqS7uv prp94sh2Kg9XmQDmS46FbsRx1IxeXvsZkW4Mw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=NjeJI27kQyu9fy17tF1hU+h+3miqCr6tcCEJAMLx968qKw8D8BXqNh4+TNqEbJzaCf PFQPJOwriz7hGlj7VfHGcglEEJvcZd3LL9G2wC3TM1WrMRuuWyzo3ptxpPSiPnTpWb1G uJNz6FfLc7M3lVCzLg0ytBexxOgmcvQbyW+7s= Received: by 10.231.50.145 with SMTP id z17mr7243791ibf.148.1277867587277; Tue, 29 Jun 2010 20:13:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.183.208 with HTTP; Tue, 29 Jun 2010 20:12:47 -0700 (PDT) From: Apoorv Sharma Date: Wed, 30 Jun 2010 08:42:47 +0530 Message-ID: Subject: Document Order in IndexWriter.addIndexes To: java-user@lucene.apache.org Content-Type: multipart/alternative; boundary=0015176f02ae9c1335048a36bb6a X-Virus-Checked: Checked by ClamAV on apache.org --0015176f02ae9c1335048a36bb6a Content-Type: text/plain; charset=ISO-8859-1 while calling addindexes or addindexes with no optimize can any gurantee be given about the document order in the new documents given that the order of directories/indexreader is fixed. So is it that ith document coming from jth indexreader will always have some x(i,j) position in the final merged index ? --0015176f02ae9c1335048a36bb6a--