Original Message-
> From: Jake Mannix [mailto:jake.man...@gmail.com]
> Sent: Thursday, October 08, 2009 7:24 AM
> To: java-user@lucene.apache.org
> Subject: Re: Help needed figuring out reason for maxClauseCount is set to
> 1024 error
>
> When such precision is needed, this
taphi.de
>
>
> > -Original Message-
> > From: Jake Mannix [mailto:jake.man...@gmail.com]
> > Sent: Thursday, October 08, 2009 2:35 AM
> > To: java-user@lucene.apache.org
> > Subject: Re: Help needed figuring out reason for maxClauseCount is set
: u...@thetaphi.de
> -Original Message-
> From: Jake Mannix [mailto:jake.man...@gmail.com]
> Sent: Thursday, October 08, 2009 2:35 AM
> To: java-user@lucene.apache.org
> Subject: Re: Help needed figuring out reason for maxClauseCount is set to
> 1024 error
>
> On
On Wed, Oct 7, 2009 at 4:42 PM, mitu2009 wrote:
>
> Hi,
>
> I've two sets of search indexes. TestIndex (used in our test environment)
> and ProdIndex(used in PRODUCTION environment). Lucene search query:
> +date:[20090410184806 TO 20091007184806] works fine for test index but
> gives
> this error
ecords(around 1300) than
> those in test one (around 950).
>
> Thanks for reading.
>
> --
> View this message in context:
> http://www.nabble.com/Help-needed-figuring-out-reason-for-maxClauseCount-is-set-to-1024-error-tp257
hey only differ wrt to number of
records/data.PROD index has got higher number of records(around 1300) than
those in test one (around 950).
Thanks for reading.
--
View this message in context:
http://www.nabble.com/Help-needed-figuring-out-reason-for-maxClauseCount-is-set-to-1024-error-tp2579634
