Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 34678 invoked from network); 6 Oct 2007 11:43:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Oct 2007 11:43:47 -0000 Received: (qmail 34824 invoked by uid 500); 6 Oct 2007 11:43:30 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 34803 invoked by uid 500); 6 Oct 2007 11:43:29 -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 34792 invoked by uid 99); 6 Oct 2007 11:43:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2007 04:43:29 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [72.249.39.145] (HELO hubmed.org) (72.249.39.145) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2007 11:43:32 +0000 Received: from [192.168.1.65] (host86-139-53-86.range86-139.btcentralplus.com [86.139.53.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hubmed.org (Postfix) with ESMTP id 5DE7C7C112 for ; Sat, 6 Oct 2007 11:42:41 +0000 (UTC) Message-ID: <470774AE.6070206@hubmed.org> Date: Sat, 06 Oct 2007 12:42:38 +0100 From: Alf Eaton User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: java-user@lucene.apache.org Subject: Re: Group of documents. References: <1e68ba6b0710052020p7dde2ffao291fcaf81161be6f@mail.gmail.com> In-Reply-To: <1e68ba6b0710052020p7dde2ffao291fcaf81161be6f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Raghu Ram wrote: > Hi, > We have an application in which we want to index feeds. Each feed is a > collection of articles and some other metadata. The problem is that > sometimes we want to search for feeds and sometimes for articles. As far as > I know lucene doesn't provide any abstraction for grouping its documents. > The only solution that we have in our minds now is to have two indexes one > for articles and one for feeds. There are two problems with this approach > 1) redundancy > 2) as feeds are just a collection of articles and get updated we have to > continuously update the document that represents the feed in the feed index. > Is this an efficient operation ?? > > Can we have any other solutions/hacks for this problem ?? Add a multi-valued field to each article that says which feed(s) it's found in? alf --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org