Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 95435 invoked from network); 10 Jun 2009 10:13:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jun 2009 10:13:57 -0000 Received: (qmail 80564 invoked by uid 500); 10 Jun 2009 10:14:09 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 80505 invoked by uid 500); 10 Jun 2009 10:14:09 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 80497 invoked by uid 99); 10 Jun 2009 10:14:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jun 2009 10:14:09 +0000 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: domain of aklimets@day.com designates 207.126.148.181 as permitted sender) Received: from [207.126.148.181] (HELO eu3sys201aog001.obsmtp.com) (207.126.148.181) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 10 Jun 2009 10:13:59 +0000 Received: from source ([209.85.218.226]) by eu3sys201aob001.postini.com ([207.126.154.11]) with SMTP ID DSNKSi+HUDI7aWaAcA6mHpYIZODnDc3eKINz@postini.com; Wed, 10 Jun 2009 10:13:39 UTC Received: by bwz26 with SMTP id 26so566812bwz.20 for ; Wed, 10 Jun 2009 03:13:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.252.17 with SMTP id e17mr649217mus.14.1244628816182; Wed, 10 Jun 2009 03:13:36 -0700 (PDT) In-Reply-To: <4A2F648C.5050208@brainlounge.de> References: <4A13DB7F.2000608@brainlounge.de> <4A146005.9050600@brainlounge.de> <4A2D08C6.60304@brainlounge.de> <4A2D3E7D.4000701@brainlounge.de> <4A2F648C.5050208@brainlounge.de> Date: Wed, 10 Jun 2009 12:13:36 +0200 Message-ID: Subject: Re: Controlling the Lucene indexing From: Alexander Klimetschek To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jun 10, 2009 at 9:45 AM, Bernd Fondermann wrote: >> i.e. create a regular JCR property instead of creating this >> low-level-behind-the-scences fields in lucene. then run the more >> sophisticated searches on those additional properties. > > How could that work? I could not differentiate using Lucene query field > qualifiers. For any additional metadata you want to search for, you compute it in your application (on write or in an observation listener) and put it into separate properties. These can then be used in your normal JCR Xpath or SQL search. This might not enable all advanced indexing features you can do with a plain Lucene, but should still cover a lot. And adding additional properties in JCR is fine - it's more about de-normalization than what you are typically taught with relational databases. Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com