Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: Paul Elschot <paul.elschot@xs4all.nl>
To: lucene-user@jakarta.apache.org
Subject: Re: Problem searching Field.Keyword field
Date: Thu, 10 Feb 2005 19:51:59 +0100
User-Agent: KMail/1.5.4
References: <20052817282.987755@Kelvin>
 <ed93bf83715ec490a1cda598c4878d1c@ehatchersolutions.com>
 <006801c50f98$1dc6a350$7703d00a@hypermedia.com>
In-Reply-To: <006801c50f98$1dc6a350$7703d00a@hypermedia.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502101951.59824.paul.elschot@xs4all.nl>

On Thursday 10 February 2005 18:44, Luke Shannon wrote:
> Are there any issues with having a bunch of boolean queries and than adding
> them to one big boolean queries (making them all required)?

The 1.4.3 and earlier BooleanScorer has an out of bounds exception
for "More than 32 required/prohibited clauses in query".

In the development version this restriction has gone.

The limitation of the maximum clause count (default 1024,
configurable) is still there.

Regards,
Paul Elschot


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