Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 14029 invoked from network); 23 Sep 2008 15:56:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Sep 2008 15:56:05 -0000 Received: (qmail 15346 invoked by uid 500); 23 Sep 2008 15:55:58 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 15275 invoked by uid 500); 23 Sep 2008 15:55:58 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 15070 invoked by uid 99); 23 Sep 2008 15:55:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 08:55:57 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [64.18.3.98] (HELO exprod8og109.obsmtp.com) (64.18.3.98) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 23 Sep 2008 15:54:57 +0000 Received: from source ([194.24.254.240]) by exprod8ob109.postini.com ([64.18.7.12]) with SMTP; Tue, 23 Sep 2008 08:53:09 PDT Received: from CHIRESBRIDGE.resource.corp.lcl ([10.222.68.43]) by lanresexc04.resource.corp.lcl with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Sep 2008 16:52:08 +0100 Received: from chiresexc04.resource.corp.lcl ([10.222.71.52]) by CHIRESBRIDGE.resource.corp.lcl with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Sep 2008 10:50:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: deleting record from the index using deleteByQuery method Date: Tue, 23 Sep 2008 10:50:20 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: deleting record from the index using deleteByQuery method Thread-Index: AckdNSxBSxBdZFvgQmmy4w3BpqwBQgAXoVOw References: From: "Kashyap, Raghu" To: X-OriginalArrivalTime: 23 Sep 2008 15:50:31.0620 (UTC) FILETIME=[1BD6D840:01C91D94] X-Virus-Checked: Checked by ClamAV on apache.org Thanks for your response Chris. I do see the reviewid in the index through luke. I guess what I am confused about is the field cumulative_delete. Does this have any significance to whether the delete was a success or not? Also shouldn't the method deleteByQuery return a diff status code based on if the delete was successful or not? -Raghu=20 -----Original Message----- From: Chris Hostetter [mailto:hossman_lucene@fucit.org]=20 Sent: Monday, September 22, 2008 11:30 PM To: solr-user@lucene.apache.org Subject: Re: deleting record from the index using deleteByQuery method : I am trying to delete a record from the index using SolrJ. When I : execute it I get a status of 0 which means success. I see that the : "cummulative_deletbyquery" count increases by 1 and also the "commit" : count increases by one. I don't see any decrease on the "numDocs" count. : When I query it back I do see that record again.=20 I'm not positive, but i don't think deleting by query will error if no=20 documents matched the query -- so just because it succeeds doesn't mean it=20 actually deleted anything ... are you sure '"rev.id:" + reviewId' matches=20 on the document you are trying to delete? does that search find it using=20 the default handler? (is there any analyzer weirdness?) -Hoss If you are not the intended recipient of this e-mail message, please noti= fy the sender = and delete all copies immediately. The sender believes this message and a= ny attachments = were sent free of any virus, worm, Trojan horse, and other forms of malic= ious code. = This message and its attachments could have been infected during transmis= sion. The = recipient opens any attachments at the recipient's own risk, and in so do= ing, the = recipient accepts full responsibility for such actions and agrees to take= protective = and remedial action relating to any malicious code. Travelport is not lia= ble for any = loss or damage arising from this message or its attachments. =0D