Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 8886 invoked from network); 19 Feb 2010 09:53:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Feb 2010 09:53:38 -0000 Received: (qmail 25198 invoked by uid 500); 19 Feb 2010 09:53:37 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 25119 invoked by uid 500); 19 Feb 2010 09:53:37 -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 25111 invoked by uid 99); 19 Feb 2010 09:53:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 09:53:37 +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 mreutegg@day.com designates 207.126.148.89 as permitted sender) Received: from [207.126.148.89] (HELO eu3sys201aog103.obsmtp.com) (207.126.148.89) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 19 Feb 2010 09:53:29 +0000 Received: from source ([74.125.78.150]) by eu3sys201aob103.postini.com ([207.126.154.11]) with SMTP ID DSNKS35fgmZAGtqAVsI6MBXA6jwsgh/OtUzZ@postini.com; Fri, 19 Feb 2010 09:53:08 UTC Received: by ey-out-1920.google.com with SMTP id 4so1553738eyg.22 for ; Fri, 19 Feb 2010 01:53:06 -0800 (PST) MIME-Version: 1.0 Sender: mreutegg@day.com Received: by 10.216.86.139 with SMTP id w11mr432455wee.10.1266573186358; Fri, 19 Feb 2010 01:53:06 -0800 (PST) In-Reply-To: References: <510143ac1002170722g76806f23he522cd7fc05a2499@mail.gmail.com> <697f8381002170751u6c090ae3kf413238a998ac9e6@mail.gmail.com> <91f3b2651002172339m1ce8d8ect81614644832eaa34@mail.gmail.com> Date: Fri, 19 Feb 2010 10:53:06 +0100 X-Google-Sender-Auth: 6bc17bc460e6a5db Message-ID: Subject: Re: [jr3] Search index in content From: Marcel Reutegger To: dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Feb 18, 2010 at 13:22, Alexander Klimetschek wro= te: > On Thu, Feb 18, 2010 at 08:39, Thomas M=FCller w= rote: >> For me, there are two kinds of indexes: the property/value indexes, >> and the fulltext index. > > The difficulty is that JCR queries can easily mix the use of both > indexes, ie. search for a certain node type (property/value index) and > a fulltext search of its contents. this would potentially become a major problem because it is nearly impossible to efficiently evaluate expressions with distinct index sources. e.g. consider the following simple query: //element(*, nt:resource)[jcr:contains(., 'frequent-word') this statement can be evaluated quite efficiently in lucene, but would probably become an issue when the type constraint and the fulltext expression come from distinct index structures. the only common identifier is the node id, which is not necessarily the primary id in both indices. regards marcel > I am sure we can implement this > mixed lookup ourselves, but with Lucene we already get it for free. I > would stick with Lucene, also because it is proven, active and faster > improving than we could do on our own. > > Regards, > Alex > > -- > Alexander Klimetschek > alexander.klimetschek@day.com >