Re: WildCardQuery

2004-10-04 Thread Morus Walter
Robinson Raju writes: > The way i have done is , > if there is a wildcard , Use WildCardQuery , > else other. > Here searchFields is an array which contains the column names . search > string is the value to be searched. > > if ((searchString.indexOf(IOOSConstants.ASTERISK) > -1) >

Re: WildCardQuery

2004-10-04 Thread Robinson Raju
The way i have done is , if there is a wildcard , Use WildCardQuery , else other. Here searchFields is an array which contains the column names . search string is the value to be searched. if ((searchString.indexOf(IOOSConstants.ASTERISK) > -1) || (searchString.indexOf(IOOSCo

Re: WildCardQuery

2004-10-04 Thread Stephane James Vaucher
On Fri, 1 Oct 2004, Robinson Raju wrote: > analyzer is StandardAnalyzer. > i use MultiFieldQueryParser to parse. > > The flow is this: > I have indexed a Database view. Now i need to search against a few columns > i take in the search criteria and search field , > construct a wildcard query and ad

Re: WildCardQuery

2004-10-01 Thread Robinson Raju
analyzer is StandardAnalyzer. i use MultiFieldQueryParser to parse. The flow is this: I have indexed a Database view. Now i need to search against a few columns i take in the search criteria and search field , construct a wildcard query and add it to a boolean query WildcardQuery wQuery = new W

RE: WildCardQuery

2004-09-30 Thread Stephane James Vaucher
Can you be a little more precise about how you process your documents? 1) What's your analyser? SimpleAnalyzer? 2) How do you parse the query? Out-of-the-box QueryParser? > can we not enter space or do an OR search with two words one of which > has a wildcard ? Simple answer, yes. Complicated a

RE: WildCardQuery

2004-09-30 Thread Robinson Raju
Hi , Would there be a problem if one enters space while using wildcards ? say i search for 'abc' . i get 100 hits as results 'man' gives - 200 'abc man' gives 300 but 'ab* man' 'abc ma*' ab* ma*' ab* OR ma* .. all of these return 0 results. can we not enter space or do an OR search with two wo

RE: WildCardQuery

2004-09-22 Thread Raju, Robinson (Cognizant)
Thanks a lot Paul , for solving the problem. I added booleanQuery.setMaxClauseCount(1) and there was no prob after that. Regards, Robin -Original Message- From: Raju, Robinson (Cognizant) Sent: Wednesday, September 22, 2004 8:01 PM To: 'Lucene Users List' Subject: RE: Wil

RE: WildCardQuery

2004-09-22 Thread Raju, Robinson (Cognizant)
Hi , I think it doesn't have anything to do with number of characters with a wildcard. Because 'z*' works and 'a*' does not. Does lucene have a limitation on the number of hits fetched ? The error that I get is org.apache.lucene.search.BooleanQuery$TooManyClauses at org.apache.lucene.sear

Re: WildCardQuery

2004-09-20 Thread Paul Elschot
On Tuesday 21 September 2004 06:50, Raju, Robinson (Cognizant) wrote: > Is there a limitation in Lucene when it comes to wildcard search ? > Is it a problem if we use less than 3 characters along with a > wildcard(*). > Gives me error if I try using 45* , *34 , *3 ..etc . > Too Many Clauses Error >

Re: WildcardQuery

2002-05-07 Thread Otis Gospodnetic
Yes, me too. I just tried it on some Lucene index (the search at blink.com) and it doesn't seem to work (try searching for travel and then *vel). I'm assuming the original poster confused something... Otis --- Joel Bernstein <[EMAIL PROTECTED]> wrote: > I thought Lucene didn't support left wild

Re: WildcardQuery

2002-05-07 Thread Jagadesh Nandasamy
Hi Joel, lucene does seem to support left wild cards take a look at this http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg01473.html -jaggi Joel Bernstein wrote: >I thought Lucene didn't support left wildcards like the following: > >*ucene > >- Original Message -

Re: WildcardQuery

2002-05-07 Thread Joel Bernstein
I thought Lucene didn't support left wildcards like the following: *ucene - Original Message - From: "Christian Schrader" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Monday, May 06, 2002 7:14 PM Subject: WildcardQuery > I am pretty happy with the results of Wi

Re: WildcardQuery

2002-05-06 Thread Peter Carlson
This is fixed in the nightly builds. --Peter On 5/6/02 4:14 PM, "Christian Schrader" <[EMAIL PROTECTED]> wrote: > I am pretty happy with the results of WildcardQueries like "*ucen*" that > matches lucene, but "*lucene*" doesn't match lucene. Is there a reason for > this? And what would be the p

Re: WildcardQuery

2001-12-11 Thread Otis Gospodnetic
If I understand you correctly, you tried to search for '*new*'. I believe you can't use an asterisk (*) as the first query of the query term. So, new* is valid, while *new or *new* is not. Otis --- "Serge A. Redchuk" <[EMAIL PROTECTED]> wrote: > Hello sampreet, > > Tuesday, December 11, 2001,

Re: WildcardQuery

2001-12-10 Thread Serge A. Redchuk
Hello sampreet, Tuesday, December 11, 2001, 6:44:29 AM, you wrote: sic> Hi All, sic> This must be simple enough, but can anyone please explain me when a sic> WildcardQuery is created in QueryParser i.e. what special characters in the sic> query string are required to build a WildcardQuery withi