You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Konstantyn Smirnov <in...@yahoo.com> on 2008/09/18 17:35:29 UTC

RE: WildCardQuery and TooManyClauses



Beard, Brian wrote:
> 
> 1) Extend QueryParser to override the getWildcardQuery method.
> 

Kinda late :), but I still have another question:

Who calls that getWildcardQuery() method? 

I subclassed the QueryParser, but that method does never get invoked, even
if the query contains *.

Shall I override some other methods? Or shall I call the method directly?

Thanx
-- 
View this message in context: http://www.nabble.com/WildCardQuery-and-TooManyClauses-tp16610177p19555644.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.


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


Re: WildCardQuery and TooManyClauses

Posted by Konstantyn Smirnov <in...@yahoo.com>.


Konstantyn Smirnov wrote:
> 
> So, how can I plug the WildcardFilter in, to prevent TooManyClauses? Are
> there other ways, than using the trunk? 
> 

Now I ended up in overriding also QueryParser.getPrefixQuery() method, using
ConstantScoreQuery and PrefixFilter. MaxClauseCountExc is gone, but is it
the right way?
-- 
View this message in context: http://www.nabble.com/WildCardQuery-and-TooManyClauses-tp16610177p19570188.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.


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


Re: WildCardQuery and TooManyClauses

Posted by Konstantyn Smirnov <in...@yahoo.com>.


Michael McCandless-2 wrote:
> 
> 
> It's only with the trunk version of Lucene that QueryParser calls  
> getWildcardQuery on parsing a wildcard string from the user's query.
> 
I see..

So, how can I plug the WildcardFilter in, to prevent TooManyClauses? Are
there other ways, than using the trunk? 
-- 
View this message in context: http://www.nabble.com/WildCardQuery-and-TooManyClauses-tp16610177p19557943.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.


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


Re: WildCardQuery and TooManyClauses

Posted by Michael McCandless <lu...@mikemccandless.com>.
It's only with the trunk version of Lucene that QueryParser calls  
getWildcardQuery on parsing a wildcard string from the user's query.

Mike

Konstantyn Smirnov wrote:

>
>
>
> Beard, Brian wrote:
>>
>> 1) Extend QueryParser to override the getWildcardQuery method.
>>
>
> Kinda late :), but I still have another question:
>
> Who calls that getWildcardQuery() method?
>
> I subclassed the QueryParser, but that method does never get  
> invoked, even
> if the query contains *.
>
> Shall I override some other methods? Or shall I call the method  
> directly?
>
> Thanx
> -- 
> View this message in context: http://www.nabble.com/WildCardQuery-and-TooManyClauses-tp16610177p19555644.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>


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