Return-Path: X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0FA4011C67 for ; Thu, 24 Apr 2014 14:23:33 +0000 (UTC) Received: (qmail 61814 invoked by uid 500); 24 Apr 2014 14:23:31 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 61767 invoked by uid 500); 24 Apr 2014 14:23:31 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 61759 invoked by uid 99); 24 Apr 2014 14:23:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 14:23:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.1.211.23] (HELO smtp-gw.artificial-solutions.com) (194.1.211.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 14:23:25 +0000 Received: from EXCHANGE.artificial-solutions.com (host-80-252-188-130-cust.phoneranetworks.se [80.252.188.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-gw.artificial-solutions.com (Postfix) with ESMTPS id 89A21BA43 for ; Thu, 24 Apr 2014 16:23:02 +0200 (CEST) Received: from EXCHANGE2.artificial-solutions.com (192.168.106.6) by EXCHANGE.artificial-solutions.com (192.168.106.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 16:22:14 +0200 Received: from EXCHANGE.artificial-solutions.com ([fe80::dca8:a0ea:ca7f:5b3]) by exchange2.artificial-solutions.com ([fe80::5cbe:5e96:e9e2:4046%15]) with mapi id 14.03.0158.001; Thu, 24 Apr 2014 16:23:19 +0200 From: Robert Haycock To: "users@jackrabbit.apache.org" Subject: RE: Overriding SearchIndex.updateNodes - removing Thread-Topic: Overriding SearchIndex.updateNodes - removing Thread-Index: Ac9fxYTqsm4ZmPQTR1GoTqlp48IDnAAAqEpA Date: Thu, 24 Apr 2014 14:22:13 +0000 Message-ID: <565B17AF7325C54B83DFBD01450462DA6BD5B09E@EXCHANGE.artificial-solutions.com> References: <565B17AF7325C54B83DFBD01450462DA6BD5B077@EXCHANGE.artificial-solutions.com> In-Reply-To: <565B17AF7325C54B83DFBD01450462DA6BD5B077@EXCHANGE.artificial-solutions.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [82.36.36.12] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I've just realised that the NodeState with type unstructured relates to a l= ater call to updateNodes(). The call I'm interested in is the previous one = where my deleted NodeId/NodeState appears in both add/remove. It appears that modifying or deleting, both actions result in the NodeId/N= odeState appearing in both parameters. Please could someone shed some light on how I should differentiate between = modify/delete. Or a better approach. Rob. -----Original Message----- From: Robert Haycock [mailto:Robert.Haycock@artificial-solutions.com]=20 Sent: 24 April 2014 15:05 To: users@jackrabbit.apache.org Subject: Overriding SearchIndex.updateNodes - removing Hi, Jackrabbit 2.6.4 I've overridden SearchManager.updateNodes(Iterator remove, Iterator= add) to create my own index. This index should reflect the curr= ent state so when a node is deleted it should be removed. I can see when I delete a node that the NodeId does'nt exist in remove but = there is an unstructured NodeState in add. Could someone please tell me how I can remove documents from my own index. Thanks, Rob.