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 "Serge A. Redchuk" <bi...@mail.ru> on 2001/12/11 16:23:30 UTC
Re[2]: WildcardQuery
Hello Otis,
Strongly can not agree with you, because I really _can_ search for
anything like '*new*'.
_Simply_Beacuse_I_have_working_code_that_do_it_
Here's a slice of output of my program:
Boolean wildcard search:
built query: bee*
news41:beem;
news42:beem;
news4:beem;
Boolean wildcard search:
built query: *ee
f3:qthree;
Boolean wildcard search:
built query: +be* +path:*ws42
news42:beem;
Boolean wildcard search:
built query: +path:*ws4 +be*
news4:beem;
As you can see the first search returned 3 entries, but the 3-rd -
only one. As well as the 4-th.
And the 2-nd search returned only entry "f3:qthree;"
(as we've expected: "built query: *ee").
And I've achieve it combining WildcardQueries in BooleanQuery, but
did not achieve it by simple call of QueryParser.parser.
Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
OG> If I understand you correctly, you tried to search for '*new*'. I
OG> believe you can't use an asterisk (*) as the first query of the query
OG> term. So, new* is valid, while *new or *new* is not.
OG> Otis
OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
>> 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 within
>> QueryParser?
>>
>> Moreover, when I achieved complex search like this: "path:*new*
>> comp*"
>> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
>> and
>> then got that query using boolq.toString(...); - the QueryParser
>> COULD
>> NOT parse this string !!!
>>
>> Is not it strange ? :
>>
>> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
>> :-(
>>
>> --
>> Best regards,
>> Serge mailto:bitl@mail.ru
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
OG> __________________________________________________
OG> Do You Yahoo!?
OG> Check out Yahoo! Shopping and Yahoo! Auctions for all of
OG> your unique holiday gifts! Buy at http://shopping.yahoo.com
OG> or bid at http://auctions.yahoo.com
--
Best regards,
Serge mailto:bitl@mail.ru
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Re[2]: WildcardQuery
Posted by sa...@interactive1.com.
Hello lucene users,
Thanks for the interest regarding wild card searches.
The WildcardQuery interprets * for 1 or more characters. But i had to edit
it for zero or more characters such that *place* , gives results
containing 'marketplace' and 'placed', but also for 'place', as was the
project requirement. Its only that instead of building the WildcardQuery
explicitly, I wanted it to be done by QueryParser class for code
optimization. I had posted the query for the same purpose.
Any suggestions will be quite helpful.
Thanks in advance,
Best regards,
Sampreet
> Sorry, It looks like I was wrong. I should have said that I haven't
> used WildcardQuery, but normally (i.e. not in Lucene), a few
> characters, often 3, are required before the wild card character.
> Sorry, can't help you, maybe somebody else can.
>
> Otis
>
> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
>> Hello Otis,
>>
>> Strongly can not agree with you, because I really _can_ search for
>> anything like '*new*'.
>>
>> _Simply_Beacuse_I_have_working_code_that_do_it_
>>
>> Here's a slice of output of my program:
>>
>> Boolean wildcard search:
>> built query: bee*
>> news41:beem;
>> news42:beem;
>> news4:beem;
>>
>> Boolean wildcard search:
>> built query: *ee
>> f3:qthree;
>>
>> Boolean wildcard search:
>> built query: +be* +path:*ws42
>> news42:beem;
>>
>> Boolean wildcard search:
>> built query: +path:*ws4 +be*
>> news4:beem;
>>
>> As you can see the first search returned 3 entries, but the 3-rd -
>> only one. As well as the 4-th.
>> And the 2-nd search returned only entry "f3:qthree;"
>> (as we've expected: "built query: *ee").
>>
>> And I've achieve it combining WildcardQueries in BooleanQuery, but did
>> not achieve it by simple call of QueryParser.parser.
>>
>> Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
>>
>> OG> If I understand you correctly, you tried to search for '*new*'. I
>> OG> believe you can't use an asterisk (*) as the first query of the
>> query
>> OG> term. So, new* is valid, while *new or *new* is not.
>>
>> OG> Otis
>>
>> OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
>> >> 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 within
>> >> QueryParser?
>> >>
>> >> Moreover, when I achieved complex search like this: "path:*new*
>> >> comp*"
>> >> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
>> >> and
>> >> then got that query using boolq.toString(...); - the QueryParser
>> >> COULD
>> >> NOT parse this string !!!
>> >>
>> >> Is not it strange ? :
>> >>
>> >> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
>> >> :-(
>> >>
>> >> --
>> >> Best regards,
>> >> Serge mailto:bitl@mail.ru
>> >>
>> >>
>> >> --
>> >> To unsubscribe, e-mail:
>> >> <ma...@jakarta.apache.org>
>> >> For additional commands, e-mail:
>> >> <ma...@jakarta.apache.org>
>> >>
>>
>>
>> OG> __________________________________________________
>> OG> Do You Yahoo!?
>> OG> Check out Yahoo! Shopping and Yahoo! Auctions for all of
>> OG> your unique holiday gifts! Buy at http://shopping.yahoo.com
>> OG> or bid at http://auctions.yahoo.com
>>
>>
>>
>> --
>> Best regards,
>> Serge mailto:bitl@mail.ru
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Check out Yahoo! Shopping and Yahoo! Auctions for all of
> your unique holiday gifts! Buy at http://shopping.yahoo.com
> or bid at http://auctions.yahoo.com
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org> For additional
> commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re[4]: WildcardQuery
Posted by "Serge A. Redchuk" <bi...@mail.ru>.
Hello Otis,
Tuesday, December 11, 2001, 7:07:42 PM, you wrote:
OG> Sorry, It looks like I was wrong. I should have said that I haven't
Don't mention !
OG> used WildcardQuery, but normally (i.e. not in Lucene), a few
You should take in attantion that also unix command prompt understands
'*' before anything else. I think it must be common.
OG> characters, often 3, are required before the wild card character.
OG> Sorry, can't help you, maybe somebody else can.
Maybe !
--
Best regards,
Serge mailto:bitl@mail.ru
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Re[2]: WildcardQuery
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Sorry, It looks like I was wrong. I should have said that I haven't
used WildcardQuery, but normally (i.e. not in Lucene), a few
characters, often 3, are required before the wild card character.
Sorry, can't help you, maybe somebody else can.
Otis
--- "Serge A. Redchuk" <bi...@mail.ru> wrote:
> Hello Otis,
>
> Strongly can not agree with you, because I really _can_ search for
> anything like '*new*'.
>
> _Simply_Beacuse_I_have_working_code_that_do_it_
>
> Here's a slice of output of my program:
>
> Boolean wildcard search:
> built query: bee*
> news41:beem;
> news42:beem;
> news4:beem;
>
> Boolean wildcard search:
> built query: *ee
> f3:qthree;
>
> Boolean wildcard search:
> built query: +be* +path:*ws42
> news42:beem;
>
> Boolean wildcard search:
> built query: +path:*ws4 +be*
> news4:beem;
>
> As you can see the first search returned 3 entries, but the 3-rd -
> only one. As well as the 4-th.
> And the 2-nd search returned only entry "f3:qthree;"
> (as we've expected: "built query: *ee").
>
> And I've achieve it combining WildcardQueries in BooleanQuery, but
> did not achieve it by simple call of QueryParser.parser.
>
> Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
>
> OG> If I understand you correctly, you tried to search for '*new*'.
> I
> OG> believe you can't use an asterisk (*) as the first query of the
> query
> OG> term. So, new* is valid, while *new or *new* is not.
>
> OG> Otis
>
> OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
> >> 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 within
> >> QueryParser?
> >>
> >> Moreover, when I achieved complex search like this: "path:*new*
> >> comp*"
> >> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
> >> and
> >> then got that query using boolq.toString(...); - the QueryParser
> >> COULD
> >> NOT parse this string !!!
> >>
> >> Is not it strange ? :
> >>
> >> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
> >> :-(
> >>
> >> --
> >> Best regards,
> >> Serge mailto:bitl@mail.ru
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> >> <ma...@jakarta.apache.org>
> >> For additional commands, e-mail:
> >> <ma...@jakarta.apache.org>
> >>
>
>
> OG> __________________________________________________
> OG> Do You Yahoo!?
> OG> Check out Yahoo! Shopping and Yahoo! Auctions for all of
> OG> your unique holiday gifts! Buy at http://shopping.yahoo.com
> OG> or bid at http://auctions.yahoo.com
>
>
>
> --
> Best regards,
> Serge mailto:bitl@mail.ru
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Re[4]: WildcardQuery
Posted by Benjamin Kopic <bk...@interactive1.com>.
Thank you Sergej :)
> -----Original Message-----
> From: Serge A. Redchuk [mailto:bitl@mail.ru]
> Sent: 11 December 2001 15:55
> To: Lucene Users List
> Subject: Re[4]: WildcardQuery
>
>
> Hello Benjamin,
>
> Tuesday, December 11, 2001, 5:28:46 PM, you wrote:
>
> BK> Sergej
>
> BK> Could you please provide a sample code to demonstrate how you
> did that?
>
> Of course:
> (please correct me if I'll become wrong finally, but hope that I have
> not hallucinations :-)
>
> // search function
> void searchBooleanWildcard( HashMap terms, boolean req ) throws
> IOException {
> System.out.println( "Boolean wildcard search:" );
> HashSet entries = new HashSet( terms.entrySet() );
> BooleanQuery bQuery = new BooleanQuery();
> for( Iterator it = entries.iterator(); it.hasNext(); ){
> Object itn = it.next();
> String where = (String)((Map.Entry)itn).getKey();
> String what = (String)((Map.Entry)itn).getValue();
> WildcardQuery wQuery = new WildcardQuery( new Term( where, what ) );
> //System.out.println( "Add to query: [" + where + ", " +
> what + "]" );
> bQuery.add( wQuery, req, false );
> }
> System.out.println( "built query: " + bQuery.toString( "body" ) );
> Searcher searcher = new IndexSearcher( rdir );
> this.showHits( searcher.search( bQuery ) );
> }
>
> // used at the end of the function above
> private void showHits( Hits hits ) throws IOException {
> for( int i=0; i<hits.length(); i++ ){
> System.out.println( hits.doc( i ).get( "path" ) + ":"
> + hits.doc( i ).get( "body" ) + "; Score: " + hits.score( i ) );
> };
> System.out.println( "" );
> }
>
> Please do not forget that HashMap can't contain more then one values
> with the same key. So the function searchBooleanWildcard(HashMap hmap) can
> combine search request only for different field names. (Hope that this
> explaination is quite clear).
>
> For example if we built search directories from 3 type of fields:
> ["body", "..."], ["path", "..."], ["type", "..."]
> we can add no more then 3 pairs to HashMap hmap.
>
> And an example of search:
> HashMap phQeryTerms = new HashMap();
> phQeryTerms.put( "body", "*e*n" );
> sr.searchBooleanWildcard( phQeryTerms, true );
>
> Corresponding output:
> Boolean wildcard search:
> built query: +*e*n
> news7:bean; Score: 1.0
> news73:beeemN; Score: 0.25
> news71:jEaN; Score: 0.25
>
> Of course, when the next pairs are indexed
> ( path , body ):
> "news7", "bean"
> "news71", "jEaN"
> "news72", "lion"
> "news73", "beeemN"
>
> BK> Best regards
>
> BK> Benjamin
>
> >> -----Original Message-----
> >> From: Serge A. Redchuk [mailto:bitl@mail.ru]
> >> Sent: 11 December 2001 15:24
> >> To: lucene-user@jakarta.apache.org
> >> Subject: Re[2]: WildcardQuery
> >>
> >>
> >> Hello Otis,
> >>
> >> Strongly can not agree with you, because I really _can_ search for
> >> anything like '*new*'.
> >>
> >> _Simply_Beacuse_I_have_working_code_that_do_it_
> >>
> >> Here's a slice of output of my program:
> >>
> >> Boolean wildcard search:
> >> built query: bee*
> >> news41:beem;
> >> news42:beem;
> >> news4:beem;
> >>
> >> Boolean wildcard search:
> >> built query: *ee
> >> f3:qthree;
> >>
> >> Boolean wildcard search:
> >> built query: +be* +path:*ws42
> >> news42:beem;
> >>
> >> Boolean wildcard search:
> >> built query: +path:*ws4 +be*
> >> news4:beem;
> >>
> >> As you can see the first search returned 3 entries, but the 3-rd -
> >> only one. As well as the 4-th.
> >> And the 2-nd search returned only entry "f3:qthree;"
> >> (as we've expected: "built query: *ee").
> >>
> >> And I've achieve it combining WildcardQueries in BooleanQuery, but
> >> did not achieve it by simple call of QueryParser.parser.
> >>
> >> Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
> >>
> >> OG> If I understand you correctly, you tried to search for '*new*'. I
> >> OG> believe you can't use an asterisk (*) as the first query
> of the query
> >> OG> term. So, new* is valid, while *new or *new* is not.
> >>
> >> OG> Otis
> >>
> >> OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
> >> >> 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 within
> >> >> QueryParser?
> >> >>
> >> >> Moreover, when I achieved complex search like this: "path:*new*
> >> >> comp*"
> >> >> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
> >> >> and
> >> >> then got that query using boolq.toString(...); - the QueryParser
> >> >> COULD
> >> >> NOT parse this string !!!
> >> >>
> >> >> Is not it strange ? :
> >> >>
> >> >> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
> >> >> :-(
> >> >>
>
> --
> Best regards,
> Serge mailto:bitl@mail.ru
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re[4]: WildcardQuery
Posted by "Serge A. Redchuk" <bi...@mail.ru>.
Hello Benjamin,
Tuesday, December 11, 2001, 5:28:46 PM, you wrote:
BK> Sergej
BK> Could you please provide a sample code to demonstrate how you did that?
Of course:
(please correct me if I'll become wrong finally, but hope that I have
not hallucinations :-)
// search function
void searchBooleanWildcard( HashMap terms, boolean req ) throws IOException {
System.out.println( "Boolean wildcard search:" );
HashSet entries = new HashSet( terms.entrySet() );
BooleanQuery bQuery = new BooleanQuery();
for( Iterator it = entries.iterator(); it.hasNext(); ){
Object itn = it.next();
String where = (String)((Map.Entry)itn).getKey();
String what = (String)((Map.Entry)itn).getValue();
WildcardQuery wQuery = new WildcardQuery( new Term( where, what ) );
//System.out.println( "Add to query: [" + where + ", " + what + "]" );
bQuery.add( wQuery, req, false );
}
System.out.println( "built query: " + bQuery.toString( "body" ) );
Searcher searcher = new IndexSearcher( rdir );
this.showHits( searcher.search( bQuery ) );
}
// used at the end of the function above
private void showHits( Hits hits ) throws IOException {
for( int i=0; i<hits.length(); i++ ){
System.out.println( hits.doc( i ).get( "path" ) + ":"
+ hits.doc( i ).get( "body" ) + "; Score: " + hits.score( i ) );
};
System.out.println( "" );
}
Please do not forget that HashMap can't contain more then one values
with the same key. So the function searchBooleanWildcard(HashMap hmap) can
combine search request only for different field names. (Hope that this
explaination is quite clear).
For example if we built search directories from 3 type of fields:
["body", "..."], ["path", "..."], ["type", "..."]
we can add no more then 3 pairs to HashMap hmap.
And an example of search:
HashMap phQeryTerms = new HashMap();
phQeryTerms.put( "body", "*e*n" );
sr.searchBooleanWildcard( phQeryTerms, true );
Corresponding output:
Boolean wildcard search:
built query: +*e*n
news7:bean; Score: 1.0
news73:beeemN; Score: 0.25
news71:jEaN; Score: 0.25
Of course, when the next pairs are indexed
( path , body ):
"news7", "bean"
"news71", "jEaN"
"news72", "lion"
"news73", "beeemN"
BK> Best regards
BK> Benjamin
>> -----Original Message-----
>> From: Serge A. Redchuk [mailto:bitl@mail.ru]
>> Sent: 11 December 2001 15:24
>> To: lucene-user@jakarta.apache.org
>> Subject: Re[2]: WildcardQuery
>>
>>
>> Hello Otis,
>>
>> Strongly can not agree with you, because I really _can_ search for
>> anything like '*new*'.
>>
>> _Simply_Beacuse_I_have_working_code_that_do_it_
>>
>> Here's a slice of output of my program:
>>
>> Boolean wildcard search:
>> built query: bee*
>> news41:beem;
>> news42:beem;
>> news4:beem;
>>
>> Boolean wildcard search:
>> built query: *ee
>> f3:qthree;
>>
>> Boolean wildcard search:
>> built query: +be* +path:*ws42
>> news42:beem;
>>
>> Boolean wildcard search:
>> built query: +path:*ws4 +be*
>> news4:beem;
>>
>> As you can see the first search returned 3 entries, but the 3-rd -
>> only one. As well as the 4-th.
>> And the 2-nd search returned only entry "f3:qthree;"
>> (as we've expected: "built query: *ee").
>>
>> And I've achieve it combining WildcardQueries in BooleanQuery, but
>> did not achieve it by simple call of QueryParser.parser.
>>
>> Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
>>
>> OG> If I understand you correctly, you tried to search for '*new*'. I
>> OG> believe you can't use an asterisk (*) as the first query of the query
>> OG> term. So, new* is valid, while *new or *new* is not.
>>
>> OG> Otis
>>
>> OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
>> >> 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 within
>> >> QueryParser?
>> >>
>> >> Moreover, when I achieved complex search like this: "path:*new*
>> >> comp*"
>> >> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
>> >> and
>> >> then got that query using boolq.toString(...); - the QueryParser
>> >> COULD
>> >> NOT parse this string !!!
>> >>
>> >> Is not it strange ? :
>> >>
>> >> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
>> >> :-(
>> >>
--
Best regards,
Serge mailto:bitl@mail.ru
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Re[2]: WildcardQuery
Posted by Benjamin Kopic <bk...@interactive1.com>.
Sergej
Could you please provide a sample code to demonstrate how you did that?
Best regards
Benjamin
> -----Original Message-----
> From: Serge A. Redchuk [mailto:bitl@mail.ru]
> Sent: 11 December 2001 15:24
> To: lucene-user@jakarta.apache.org
> Subject: Re[2]: WildcardQuery
>
>
> Hello Otis,
>
> Strongly can not agree with you, because I really _can_ search for
> anything like '*new*'.
>
> _Simply_Beacuse_I_have_working_code_that_do_it_
>
> Here's a slice of output of my program:
>
> Boolean wildcard search:
> built query: bee*
> news41:beem;
> news42:beem;
> news4:beem;
>
> Boolean wildcard search:
> built query: *ee
> f3:qthree;
>
> Boolean wildcard search:
> built query: +be* +path:*ws42
> news42:beem;
>
> Boolean wildcard search:
> built query: +path:*ws4 +be*
> news4:beem;
>
> As you can see the first search returned 3 entries, but the 3-rd -
> only one. As well as the 4-th.
> And the 2-nd search returned only entry "f3:qthree;"
> (as we've expected: "built query: *ee").
>
> And I've achieve it combining WildcardQueries in BooleanQuery, but
> did not achieve it by simple call of QueryParser.parser.
>
> Tuesday, December 11, 2001, 4:22:04 PM, you wrote:
>
> OG> If I understand you correctly, you tried to search for '*new*'. I
> OG> believe you can't use an asterisk (*) as the first query of the query
> OG> term. So, new* is valid, while *new or *new* is not.
>
> OG> Otis
>
> OG> --- "Serge A. Redchuk" <bi...@mail.ru> wrote:
> >> 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 within
> >> QueryParser?
> >>
> >> Moreover, when I achieved complex search like this: "path:*new*
> >> comp*"
> >> by combining WildcardQueries in BooleanQuery (NOT BY QueryParser),
> >> and
> >> then got that query using boolq.toString(...); - the QueryParser
> >> COULD
> >> NOT parse this string !!!
> >>
> >> Is not it strange ? :
> >>
> >> QueryParser.parse( bquery.toString( ... ) ) .... - do not work
> >> :-(
> >>
> >> --
> >> Best regards,
> >> Serge mailto:bitl@mail.ru
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> >> <ma...@jakarta.apache.org>
> >> For additional commands, e-mail:
> >> <ma...@jakarta.apache.org>
> >>
>
>
> OG> __________________________________________________
> OG> Do You Yahoo!?
> OG> Check out Yahoo! Shopping and Yahoo! Auctions for all of
> OG> your unique holiday gifts! Buy at http://shopping.yahoo.com
> OG> or bid at http://auctions.yahoo.com
>
>
>
> --
> Best regards,
> Serge mailto:bitl@mail.ru
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>