From dev-return-13559-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Aug 22 11:43:43 2007 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 45302 invoked from network); 22 Aug 2007 11:43:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2007 11:43:42 -0000 Received: (qmail 56662 invoked by uid 500); 22 Aug 2007 11:43:38 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 56635 invoked by uid 500); 22 Aug 2007 11:43:38 -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 56626 invoked by uid 99); 22 Aug 2007 11:43:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 04:43:38 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [213.133.33.40] (HELO smtp.is.nl) (213.133.33.40) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 11:44:12 +0000 Received: from [213.133.51.241] (HELO hai01.hippo.local) by smtp.is.nl (CommuniGate Pro SMTP 5.0.10) with ESMTP id 22150386 for dev@jackrabbit.apache.org; Wed, 22 Aug 2007 13:43:14 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6619.12 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7E4B1.9F32F432" Subject: RE: IndexingConfiguration jr 1.4 release, analyzing, searching and synonymprovider Date: Wed, 22 Aug 2007 13:43:13 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IndexingConfiguration jr 1.4 release, analyzing, searching and synonymprovider Thread-Index: AcfkrqKWwawyoN5PSOuf0HhmbAcDnAAAgVi+ References: From: "Ard Schrijvers" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C7E4B1.9F32F432 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable > for each field that have it configured like this. Since this analyzer = is used for indexing > *and* querying, on a per field basis, it will always work.... Bertrand Delacretaz wrote:=20 -------------------------- Sure, but what happens with Marcel's previous example (earlier in this = thread): //*[jcr:contains(., 'h=E4gar')] You won't know which field name to use to select an Analyzer, hence the need for a configurable default analyzer for queries. That's unless the above query translates to a big OR statement where each field is queried with its own analyzer, I don't know how it is currently implemented.=20 -------------------------- The node scope query will always be performed with the default Analyzer. = As one single lucene Document contains a full indexed Field of all = properties (all analyzed with the default analyzer), and a indexed Field = for each seperate property (possibly with some custom analyzer), this = should not be a real problem. Think it takes some documentation that = explains that in rare cases when you use specific property analyzers you = may find a different result when searching in a property then when = searching in the node scope.=20 Regards Ard ------_=_NextPart_001_01C7E4B1.9F32F432--