Hi,
first of all you'll never get TooManyClauseException because you're sesarching for phrase query. (i.e. this query will not be rewrited into boolean query).
about your question: if you need search like 123* you can use some term as begining marker and include this term at the begining of phrase query. But if prefix is long enough then ordinary PrefixQuery can win in speed. (it can vary depending on indexing conditions)
Regards, Volosymyr Bychkoviak.
Aalap Parikh wrote:
Hi,
Thanks for your reply. One more question. You mentioned that your technique can be used for wildcard search like ex. *123* . But say I only need something like 123* i.e. wildcard only at the end and NOT on both sides, then how can one use your technique to avoid TooManyClauseException?
Thanks, Aalap.
--- Volodymyr Bychkoviak <[EMAIL PROTECTED]>
wrote:
I used It to measure speed and but I was planning---------------------------------------------------------------------
to use it in file search application. when u need wildcard search like
*.txt and so on. The matter is that file search application is not
my primary job, so I will tune it later.
This is just an example to give you an idea how it
can work.
regards, Volodymyr Bychkoviak
Aalap Parikh wrote:
IHi,
Also this analyzer is not used in any application,
---------------------------------------------------------------------wrote it only to measure search speed.
So you don't use the method you described for your wildcard search trick?
Thanks, Aalap.
To unsubscribe, e-mail:[EMAIL PROTECTED]
For additional commands, e-mail:[EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
