Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 92563 invoked from network); 3 Jun 2002 05:01:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Jun 2002 05:01:48 -0000 Received: (qmail 5077 invoked by uid 97); 3 Jun 2002 05:01:57 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 5060 invoked by uid 97); 3 Jun 2002 05:01:57 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 5048 invoked by uid 98); 3 Jun 2002 05:01:56 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Errors-To: User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Sun, 02 Jun 2002 22:01:51 -0700 Subject: Re: Bug? QueryParser may not correctly interpret RangeQuery text From: Peter Carlson To: Lucene Developers List Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I think that it is fairly intuitive depending on what functionality people are trying to use. For just a standard set of terms the big question is what should the default boolean operator be OR or AND. For the rest, it seems fairly "standard" when looking at other search engine syntax. Also, when a user wants the added functionality it's available just by reading some documentation. Searching by field, phrase queries, sub queries, fuzzy searches, boosting terms, proximity operators. >From my perspective selling a product that depends on the search engine, people ask about the complex search features, but often don't use them (although they would down grade the product unless it had them). It's very nice to be able to say we have the functionality, and it's one of the reasons why we choose Lucene because it was so full featured from the get go. --Peter On 6/2/02 9:40 PM, "Eric D. Friedman" wrote: > I agree with Alex -- the QueryParser's syntax has become > at least as obfuscated as SQL, probably more so. It may > have started out simple, but it's not simple anymore. > > Eric -- To unsubscribe, e-mail: For additional commands, e-mail: