Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 86169 invoked from network); 29 Dec 2008 21:38:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Dec 2008 21:38:45 -0000 Received: (qmail 15189 invoked by uid 500); 29 Dec 2008 21:38:43 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 15171 invoked by uid 500); 29 Dec 2008 21:38:43 -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 15160 invoked by uid 99); 29 Dec 2008 21:38:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Dec 2008 13:38:43 -0800 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 [213.133.51.241] (HELO mail.hippo.nl) (213.133.51.241) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Dec 2008 21:38:35 +0000 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: how to make the path name searchable Date: Mon, 29 Dec 2008 22:38:07 +0100 Message-ID: In-Reply-To: <30998.69783.qm@web82604.mail.mud.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: how to make the path name searchable Thread-Index: Acln0oZBC6si+YyTR7anx4KGlZzpdACKm0Ig References: <30998.69783.qm@web82604.mail.mud.yahoo.com> From: "Ard Schrijvers" To: X-Virus-Checked: Checked by ClamAV on apache.org =20 Hello Kevin, It is not possible without extending the Jackrabbit SearchIndex (and having implication for moving nodes as well, because you have to re-save the entire subtree). Furthermore, the design is to not have any path information in the index or in nodestates. This ensures move operation to be leight, no matter how large the subtree below the node to move. This wouldn't be possible if you would store path information. I also think you'll run into really nasty issues in case of same name sibblings. Last but not least, I doubt whether having a search result based on path info is a good strategy anyway... Ard >=20 > Hi, >=20 > Hope it's not a silly question -- is it possible to make the=20 > path name searchable? For example, I have a product at=20 > /electronics/camera/canon/hf100. I would like the path=20 > /electronics/camera/canon included in the search result if I=20 > search for 'canon'.=20 >=20 > Thanks a lot, > Kevin >=20 >=20