Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 82175 invoked from network); 17 Aug 2007 16:36:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Aug 2007 16:36:00 -0000 Received: (qmail 73845 invoked by uid 500); 17 Aug 2007 16:35:58 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 73475 invoked by uid 500); 17 Aug 2007 16:35:57 -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 73466 invoked by uid 99); 17 Aug 2007 16:35:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2007 09:35:57 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gcaj-jackrabbit-dev@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2007 16:36:16 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IM4nK-00085L-Nq for dev@jackrabbit.apache.org; Fri, 17 Aug 2007 18:35:30 +0200 Received: from gateway.subshell.com ([212.79.22.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Aug 2007 18:35:30 +0200 Received: from christoph by gateway.subshell.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Aug 2007 18:35:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@jackrabbit.apache.org From: Christoph Kiehl Subject: Re: improving the scalability in searching Date: Fri, 17 Aug 2007 18:34:34 +0200 Lines: 31 Message-ID: References: <46C5A4AA.7030907@gmx.net> <46C5C578.7080003@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gateway.subshell.com User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <46C5C578.7080003@gmx.net> Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Marcel Reutegger wrote: > 1) New QueryHandler class > 2) Introduce parameter in configuration > 3) Auto-detect in SearchIndex > > I prefer 1) because it makes it explicit. I have reservations regarding > 3) because it introduces some magic. I don't like 2) because we probably > cannot come up with a sensible name ;) I'm a bit indifferent about 1) because I think the change is not fundamentally enough to justify a new QueryHandler class. Do you have any other plans with the new QueryHandler implementation? If I were to implement a SQL based QueryHandler solution I would create a new QueryHandler implementation, but not for a small change like that. Why don't you like my suggestion to replace the old behaviour using the strategy pattern? Just because you have to specify or auto-detect which strategy to use? Or is there any other reason? I don't like 2) as well because I prefer 3) ;). I would like to reduce the number of choices for the user (see i.e. http://www.joelonsoftware.com/items/2006/11/21.html). The system should just work optimally by itself. Which problem do you see in not explicitly stating in the configuration which index format is used? The only reason I could come up with is for people not knowing which format they use. But I would just log a warning if the index is in the old format and that query performance will improve if they rebuild their indexes. I don't want to be academically, I just want the best solution for the user. I wouldn't object if you decide to go for 1). It's just that I would like to understand your reasoning. Cheers & a happy weekend ;) Chris