lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: VOTE: BooleanQuery$TooManyClauses
Date Mon, 01 Dec 2003 23:33:37 GMT
On Monday, December 1, 2003, at 01:02  PM, Doug Cutting wrote:
> Wow!  What a tempest in a teapot this one has become!

Oops... sorry!

> Here are the options as I see them.
>
> 3. Change TooManyClauses to extend IOException.
>
> IOException is already thrown by all of the search methods in 
> question, so that applications must already deal with this.  This is 
> not ideal, as the condition doesn't actually involve i/o, but 
> IOException is already effectively used as LuceneException.  (In a 2.0 
> release we should, as Erik suggests, rationalize Lucene's exceptions.)
>
> Thus I propose to implement (3).  Votes?

What about leave it as-is?  My only beef was with QueryParser throwing 
something other than ParseException.  I personally haven't run into 
this issue.

I'm find with option 3, if a change must be made.

	Erik


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


Mime
View raw message