: Or, to avoid the clause limit issue altogether, you could use a
: PrefixFilter instead of a QueryWrapperFilter around a
: {Wildcard,Prefix}Query:
right ... the missconception here seems to be that if you use a Filter,
all your Too Many Clauses problems are sovled -- but if that Filter is
ju
Hi René,
Since you're constructing the filter from a WildcardQuery or a PrefixQuery,
both of which use a BooleanQuery to hold a TermQuery for each matching index
term, you'll need to increase the number of clauses a BooleanQuery is allowed
to hold, by calling static method BooleanQuery.setMaxCl
Betreff: Re: too many clause exception when using a filter
> Hi,
>
> Try using PrefixQuery? Is it still throws exception?
>
> Regards
> Ganesh
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To:
> Sent: Wednesday, July 30, 2008 1:00 PM
>
Hi,
Try using PrefixQuery? Is it still throws exception?
Regards
Ganesh
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Wednesday, July 30, 2008 1:00 PM
Subject: too many clause exception when using a filter
Hello,
I've filled an index with 1100 text fil
Hello,
I've filled an index with 1100 text files with the names "monisys1" to
"monisys1100".
If I start a WildcardQuery
WildcardQuery query = new WildcardQuery(new Term("fileId","monisys*"));
Hits hits = searcher.search(query);
I get a "Too many clauses" exception, like I expecte
