Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 10720 invoked from network); 28 Aug 2007 09:35:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Aug 2007 09:35:54 -0000 Received: (qmail 9151 invoked by uid 500); 28 Aug 2007 09:35:49 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 9127 invoked by uid 500); 28 Aug 2007 09:35:49 -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 9117 invoked by uid 99); 28 Aug 2007 09:35:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 02:35:49 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 09:36:45 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9F96D714210 for ; Tue, 28 Aug 2007 02:35:30 -0700 (PDT) Message-ID: <32850600.1188293730633.JavaMail.jira@brutus> Date: Tue, 28 Aug 2007 02:35:30 -0700 (PDT) From: "Marcel Reutegger (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1079) Extend the IndexingConfiguration to allow configuration of reuseable analyzers In-Reply-To: <16833397.1187859030703.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523203 ] Marcel Reutegger commented on JCR-1079: --------------------------------------- That's OK with me, but I think being able to configure an analyzer in an index rule also seems useful to me. > Extend the IndexingConfiguration to allow configuration of reuseable analyzers > ------------------------------------------------------------------------------ > > Key: JCR-1079 > URL: https://issues.apache.org/jira/browse/JCR-1079 > Project: Jackrabbit > Issue Type: New Feature > Affects Versions: 1.3.1 > Reporter: Ard Schrijvers > Priority: Minor > Fix For: 1.4 > > > To the indexing_configuration.xml a xml block of analyzers should be configurable. In each to a property an analyzer can be assigned. This means, that property will be analyzed with that specific analyzer. In the first place, it enables multilingual indexing. > Documentation needs to be added explaining the difference in searching in the node scope [jcr:contains(.,'foo')] and in some property [jcr:contains(@myprop,'foo')]. The node scope will always be searched and indexed with the default analyzer, which can be configured in the workspace.xml in the element. > Below a possible indexing_configuration.xml snippet is shown. Also node the possible enhancement (not sure wether this implementation will have it, because it requires a lot of filter Factories and is probably out of scope). Adding custom filters which do not need a factory might be easier. > > > > > > > > > > bode_fr > bode_de > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.