Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 51194 invoked from network); 13 Oct 2010 20:55:16 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Oct 2010 20:55:16 -0000 Received: (qmail 1921 invoked by uid 500); 13 Oct 2010 20:55:14 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 1871 invoked by uid 500); 13 Oct 2010 20:55:14 -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 1863 invoked by uid 99); 13 Oct 2010 20:55:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Oct 2010 20:55:14 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.139.52.240] (HELO nm25-vm0.bullet.mail.ac4.yahoo.com) (98.139.52.240) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 13 Oct 2010 20:55:07 +0000 Received: from [98.139.52.195] by nm25.bullet.mail.ac4.yahoo.com with NNFMP; 13 Oct 2010 20:54:46 -0000 Received: from [98.139.52.184] by tm8.bullet.mail.ac4.yahoo.com with NNFMP; 13 Oct 2010 20:54:46 -0000 Received: from [127.0.0.1] by omp1067.mail.ac4.yahoo.com with NNFMP; 13 Oct 2010 20:54:46 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 89002.36226.bm@omp1067.mail.ac4.yahoo.com Received: (qmail 43707 invoked by uid 60001); 13 Oct 2010 20:54:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1287003285; bh=jkS3V26vpQEan5yIiH/unk5gFDrqtyUOA1yVZUqOHJg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=cICCD1dKTwut9EA5IyRShK/nyqvQKYw4MH3FmGVQgn2CrK++sadwrBKmkelAu5yXs+Cb8Ut/O4LWvRO77oKQps1leoTAWgCcsDw0XtqqSoN2nkC3P9H3SUdc0cOcDP/MIohs67vbPOOQUHcEjKvecRU88qSYjBlAdlNa1LpVqHQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=BruVkj23b7jMhyzY+kXuv7wuQ/BlZJWnMWCwix7eRcJI+60YIuq/I/emoU3mpERoGesslRwuUevDJVuP7X8gzi2RZtIc5amNa6bLxy7jPZ0gu3spBdNamG28R2NnIQLCZ4am1FsNmBHecjsh/uAn9C0o7ybrTVKC2sYWAxjzCY0=; Message-ID: <898709.38710.qm@web50306.mail.re2.yahoo.com> X-YMail-OSG: oRpsRw0VM1m_vEnUQLkFRTvvv7BA8WMxDEukFNuWu6d7Mbt 8me81FBXtviDvAPzkxBb9RO.jQ0f2myqw5yN5aI1SoIoloKD_D7iCfBzKqnt bUKfEqfj2IXqaitE3iQFzdMxn4MT5BLFtCGBh2ov_cW_AHBphr6XgxJQfwe0 sS3PUOyVjUAuiG.aoFlrTVM9t0FbjHjVAncRDK1Xa4x3vU.DQvczxeAEy2Nw 484ZyACfaSUDQh8_5fVq_GJV8d5zIGIVRKToLjBE2xo_4HrcIsdSw_AoyqWZ JqxZ6vaS_xsHfN98BO47ogEXO.xU6ZwCGsmMGisIXfHKUClDDhTO7fID46s3 esTyKpBU- Received: from [184.75.0.186] by web50306.mail.re2.yahoo.com via HTTP; Wed, 13 Oct 2010 13:54:45 PDT X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.106.282862 References: <3B4AEBB59588ED409ECE3CB6517C417510C036EB23@exchange.windows.mmu.acquiremedia.com> Date: Wed, 13 Oct 2010 13:54:45 -0700 (PDT) From: Otis Gospodnetic Subject: Re: How about lucene's delete performance ? To: java-user@lucene.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hello, Of course, if you actually want the last 7 days rolling effect and not the this week vs. previous week, then you could go with smaller indices, say daily ones. Then you'd always add new docs to the latest index and removing the oldest index completely every 24 hours. You could go hourly, too, depending on your exact needs. Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ ----- Original Message ---- > From: Shai Erera > To: java-user@lucene.apache.org > Sent: Wed, October 13, 2010 11:06:46 AM > Subject: Re: How about lucene's delete performance ? > > Note that deleteAll does not require you to optimize anything. It literally > removes all segments from the index in one shot, and when the files are > unreferenced, they will be removed entirely. > > Shai > > On Wed, Oct 13, 2010 at 4:53 PM, Dan OConnor wrote: > > > Jeff, > > I would suggest not deleting documents off the back of the index unless you > > can optimize your index regularly. (Depending on your volume, this could be > > every day or once a week) > > > > I would suggest having two indexes, one that is "this" week and one that is > > "last" week and a multi-index searcher that is aware of the date. When you > > get to the end of "this" week, you would delete "last" week's index and > > create a new "next" week index. > > > > Regards > > Dan > > > > > > ----- Original Message ----- > > From: Jeff Zhang > > To: java-user@lucene.apache.org > > Sent: Wed Oct 13 09:37:31 2010 > > Subject: How about lucene's delete performance ? > > > > Hi all, > > > > I only want to index the latest one week's data, the previous data can > > be deleted. So I'd like to know about lucene's delete performance and > > whether it will has impact on the search performance when I do lots of > > delete operation in the meantime. Thanks > > > > -- > > Best Regards > > > > Jeff Zhang > > > > --------------------------------------------------------------------- > > 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