Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 417B9107F3 for ; Wed, 14 Aug 2013 16:35:48 +0000 (UTC) Received: (qmail 3479 invoked by uid 500); 14 Aug 2013 16:35:45 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 3396 invoked by uid 500); 14 Aug 2013 16:35:45 -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 Delivered-To: moderator for java-user@lucene.apache.org Received: (qmail 99874 invoked by uid 99); 14 Aug 2013 09:04:09 -0000 X-ASF-Spam-Status: No, hits=4.1 required=5.0 tests=HTML_MESSAGE,SPF_HELO_SOFTFAIL,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of jason.nacional@icomteq.com does not designate 61.14.179.242 as permitted sender) From: "Mark Jason B. Nacional" To: "java-user@lucene.apache.org" Subject: Assistance for Unified Index Proces Thread-Topic: Assistance for Unified Index Proces Thread-Index: Ac6YzSIL60DDyOmjS8GFOPSzhCFDbQ== Date: Wed, 14 Aug 2013 09:03:24 +0000 Message-ID: <4DB7F1DF50584D428AEDC9FFA01D23BA61F3A56C@mail1.icomteq.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_4DB7F1DF50584D428AEDC9FFA01D23BA61F3A56Cmail1icomteqloc_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_4DB7F1DF50584D428AEDC9FFA01D23BA61F3A56Cmail1icomteqloc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Lucene Developers: I just want to ask some help regarding our new implementation of indexing p= rocess. We use this API for searching a number of documents in a review platform (e= -discovery). On our search module, we index a document per folder. The problem is that a= user can create his own folder. Right now, what our developers implemented was to create an index file of a= ll folders. So imagine if a user will have to select a multiple source fold= er, we have to iterate to all its index files to get the results. I was assigned to change this implementation. They called it "Unified Index= ". In this implementation, we have only one index file to manage. I just want to get information as to how am I going to implemented it in a = an optimal way. Any suggestion would be perfect! :) Thanks! Mark Jason Nacional Junior Software Engineer --_000_4DB7F1DF50584D428AEDC9FFA01D23BA61F3A56Cmail1icomteqloc_--