Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Date: Wed, 26 Nov 2003 12:14:18 -0500
Subject: Re: Why does BooleanQuery$TooManyClauses extend RuntimeException?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Erik Hatcher <erik@ehatchersolutions.com>
To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <63733575-2033-11D8-98ED-000393A564E6@ehatchersolutions.com>
Message-Id: <F7DC677D-2033-11D8-98ED-000393A564E6@ehatchersolutions.com>

On Wednesday, November 26, 2003, at 12:10  PM, Erik Hatcher wrote:
>
> On Wednesday, November 26, 2003, at 11:44  AM, Doug Cutting wrote:
>> Erik Hatcher wrote:
>>> I concur and have just modified QueryParser to throw a 
>>> ParseException instead when a TooManyClauses exception is thrown.
>>
>> When using a prefix or wildcard query (where this is most likely to 
>> occur) I don't think TooManyClauses is thrown under the parser, but 
>> rather when searching, as the query isn't rewritten until it's 
>> executed.
>
> If that was the case, then this test would fail, right?
>
>   public void testBooleanQuery() throws Exception {
>     BooleanQuery.setMaxClauseCount(2);
>     try {
>       QueryParser.parse("one two three", "field", new 
> WhitespaceAnalyzer());
>       fail("ParseException expected due to too many boolean clauses");
>     } catch (ParseException expected) {
>       // too many boolean clauses, so ParseException is expected
>     }
>   }
>
> But it passes.

Nevermind.... my test is not for prefix or wildcard query, but it does 
show that TooManyClauses can be thrown from QueryParser.parse, which I 
still feel deserves a ParseException.


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