Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 87156 invoked from network); 12 Mar 2006 07:47:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Mar 2006 07:47:21 -0000 Received: (qmail 2566 invoked by uid 500); 12 Mar 2006 07:47:16 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 2538 invoked by uid 500); 12 Mar 2006 07:47:16 -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 2526 invoked by uid 99); 12 Mar 2006 07:47:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Mar 2006 23:47:16 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.143.78.232] (HELO xmail.me.corp.entopia.com) (212.143.78.232) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Mar 2006 23:47:15 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message Subject: RE: Alternate Use of Lucene MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 12 Mar 2006 09:46:52 +0200 Message-ID: <39B0FB508E5D7540ACA5AD57225E150D392107@xmail.me.corp.entopia.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Alternate Use of Lucene Thread-Index: AcZEcgjmoinK/J/yQ5WygcQY8xR/sgBNoXRQ From: "Andrew Schetinin" To: , X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi James, >From one side, it is easy - you simply enumerate all the found objects, and for each object retrieve the field Supervisor, sorting and removing duplicates on the fly. >From the other side, this way you'll get linear performance, and even worse - retrieving fields is not a very fast operation. But there is no other way to do it in Lucene, AFAIK. Lucene was not designed for such usage. Best Regards, Andrew -----Original Message----- From: James Cook [mailto:djamescook@gmail.com]=20 Sent: Friday, March 10, 2006 8:39 PM To: java-user@lucene.apache.org Subject: Alternate Use of Lucene Is there a technique, using Lucene, to retrieve the remaining index values from the results of a query? Here is a better explanation of the question. I have various fields that have been indexed on a particular collection of Java POJO's. For example, an Employee object may have the following fields: id, salary, hire date, termination date, department, supervisor, etc.. I want to issue a query such as "department: 15". This restricts my list of Employee objects to those with a department value of 15. What may be a little different at this stage is I don't care about the resulting Employee list. What I really want is access to the Lucene index values for the 'supervisor' field. Basically, I want a list of those supervisors for the resulting filtered list of Employees. Does lucene provide an API to access these values? --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org