Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of erickerickson@gmail.com
 designates 209.85.142.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=meTLbD5BhULgHF3wxlz2fosvtj0FxYaj0YYOx3uCDHsIwa2anUFP6xUF+Q7rVwX+Q+
         oF5sXuTJdcix32uUXfbLmNFBE3L7B7+5tELJz2pWRYnsz2ZdIr/+y6eCPLKYYXBZdtls
         UP3qOQwNLwFLm6yEvT3/VY+YAXcihyaGZcZHo=
Message-ID: <359a92830807070919y550b73d9wef38df149a9535e5@mail.gmail.com>
Date: Mon, 7 Jul 2008 12:19:58 -0400
From: "Erick Erickson" <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: disable boolean operators ?
In-Reply-To: <0833DC23-F7DB-412F-885E-E99FEE3C87CB@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_19000_6087377.1215447598197"
References: <0833DC23-F7DB-412F-885E-E99FEE3C87CB@gmail.com>

------=_Part_19000_6087377.1215447598197
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think you're off base a little. Lucene defaults to 1,024 boolean clauses
as the maximum number allowed. There is an implied boolean between
each term no matter what. Removing OR, AND, NOT doesn't change
that in the least. That is,
term1 term2 term3
is equivalent to
term1 OR term2 OR term3

So removing the booleans is having no effect on the error. The fact
that you have over 2,000 terms is the issue.

But you can change the number by BooleanQuery.setMaxClauseCount

Best
Erick

On Mon, Jul 7, 2008 at 12:04 PM, Balthasar Schopman <lstitchvu@gmail.com>
wrote:

> Hiya,
>
> Is there a way to disable boolean operators in the Lucene engine?
>
> The reason for this question is the mystical / unexpected exception I
> encounter when parsing a query containing many words. I query on a single
> field with a query containing 2243 words (14.742 characters). I haven't had
> this issue with smaller queries. I remove the Lucene special characters (+,
> -, &&, ||, !, (, ), {, }, [, ], ^, \, ~, *, ?, :, \) and boolean operators
> (AND, OR, NOT) from string before including them in a query. Then I
> construct the query as follows:
> Query q = new QueryParser("alldata", analyser).parse(queryString);
> and call
> Hits hits = searcher.search(q);
>
> An exception with the following message is thrown:
> Cannot parse '<big string>': too many boolean clauses
>
> Kind regards,
> Balthasar Schopman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

------=_Part_19000_6087377.1215447598197--