Re: WildCard search replacement

Glad to help you. Aalap Parikh wrote: Thanks very much. Volodymyr, your trick about wildcard search replacement has helped me a lot. Great idea!!! Thanks a lot again. --- Volodymyr Bychkoviak <[EMAIL PROTECTED]> wrote: Hi. Aalap Parikh wrote: Hi, The idea about begin marker sound

Re: WildCard search replacement

Thanks very much. Volodymyr, your trick about wildcard search replacement has helped me a lot. Great idea!!! Thanks a lot again. --- Volodymyr Bychkoviak <[EMAIL PROTECTED]> wrote: > Hi. > > Aalap Parikh wrote: > > >Hi, > > > >The idea about begin marker sou

Re: WildCard search replacement

Hi. Aalap Parikh wrote: Hi, The idea about begin marker sounds good. And the prefix could be anything and could be made really small by just using may be 2 or 3 or even less characters. if you want to use 1 character for begin marker make sure you don't nave same tokens. But I think that making

Re: WildCard search replacement

Hi, The idea about begin marker sounds good. And the prefix could be anything and could be made really small by just using may be 2 or 3 or even less characters. In terms of the PrefixQuery for 123* wildcard search, wouldn't such a query be rewritten to a BooleanQuery? I tried using PrefixQuery a

Re: WildCard search replacement

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 phr

Re: WildCard search replacement

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

Re: WildCard search replacement

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. reg

Re: WildCard search replacement

Hi, > Also this analyzer is not used in any application, I > 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 PR

Re: WildCard search replacement

Aalap Parikh wrote: Hi Volodymyr, About the trick you described about wildcard search replacement, you mentioned: So I found following workaround. I index this field as > sequence of terms, each of containing single digit from > needed value. (For example I have “123214213” value

WildCard search replacement

Hi Volodymyr, About the trick you described about wildcard search replacement, you mentioned: > So I found following workaround. I index this field as > sequence of terms, each of containing single digit from > needed value. (For example I have “123214213” value > that needs to be i

Re: WildCard search replacement

That's a great technique - thanks for sharing it! Erik On Mar 14, 2005, at 6:54 AM, Volodymyr Bychkoviak wrote: Hi all. I have large index of documents (about 1.6 millions) One field (for example called “number”) contains string of digits. I need to do wildcard search on this field such as

WildCard search replacement

Hi all. I have large index of documents (about 1.6 millions) One field (for example called “number”) contains string of digits. I need to do wildcard search on this field such as “*expression*” (i.e. all documents that contains “expression” in this field. When I run such search with very short e