[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    Re: QueryParser refactoring
From:       Morus Walter <morus.walter () tanto ! de>
Date:       2005-03-08 14:20:18
Message-ID: 16941.46242.773831.529161 () tanto-xipolis ! de
[Download RAW message or body]

Daniel Naber writes:
> On Tuesday 08 March 2005 14:46, Erik Hatcher wrote:
> 
> > > Right. `a AND (NOT b)'  parses to `a'
> >
> > Is this what we want to happen for a general purpose next generation
> > Lucene QueryParser though?  I'm not sure.  Perhaps this should be a
> > ParseException instead?
> 
> As we have no concept of a "warning" we should indeed prefer to throw an 
> exception instead of silently modifying the query in ways the users don't 
> expect.
> 
Shouldn't that imply that search itself also throws an exception if it
has to execute such a query?
AFAIK silently ignoring that query is what is currently happening during 
search.

Morus

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]