Fwd: Wildcard query parser of MultiFieldQueryParser should support boosts

2017-08-17 Thread Yegor Dovganich
Hello, can someone review my patch? https://issues.apache.org/jira/browse/LUCENE-7917 -- Regards, Yegor Dovganich - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h..

AW: negative wildcard query

2011-06-30 Thread Clemens Wyss
Thx! > -Ursprüngliche Nachricht- > Von: Uwe Schindler [mailto:u...@thetaphi.de] > Gesendet: Donnerstag, 30. Juni 2011 10:32 > An: java-user@lucene.apache.org > Betreff: RE: negative wildcard query > > Pure negative queries do not work, you have to add a MUST c

RE: negative wildcard query

2011-06-30 Thread Uwe Schindler
- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Clemens Wyss [mailto:clemens...@mysign.ch] > Sent: Thursday, June 30, 2011 9:44 AM > To: java-user@lucene.apache.org > Subject: AW: negative wild

AW: negative wildcard query

2011-06-30 Thread Clemens Wyss
@mysign.ch] > Gesendet: Donnerstag, 30. Juni 2011 05:37 > An: java-user@lucene.apache.org > Betreff: AW: negative wildcard query > > Karl, I just saw, that I had a typo in my initial post. It should be: > > Say I have a document with a single field "f". How can I se

AW: negative wildcard query

2011-06-29 Thread Clemens Wyss
s... Any advices? Thx Clemens > -Ursprüngliche Nachricht- > Von: Karl Wettin [mailto:karl.wet...@gmail.com] > Gesendet: Mittwoch, 29. Juni 2011 22:36 > An: java-user@lucene.apache.org > Betreff: Re: negative wildcard query > > You'll also need things to exclude f

Re: negative wildcard query

2011-06-29 Thread Karl Wettin
You'll also need things to exclude from, eg a MatchAllDocsQuery. karl 29 jun 2011 kl. 17.25 skrev Clemens Wyss: > Say I have a document with field "f1". How can I search Documents which have > not "test" in field "f" > I tried: > -f: *test* > f: -*test* > f: NOT *test* > > but no luck.

negative wildcard query

2011-06-29 Thread Clemens Wyss
Say I have a document with field "f1". How can I search Documents which have not "test" in field "f" I tried: -f: *test* f: -*test* f: NOT *test* but no luck. Using WildCardQuery class... Any advices? Thx Clemens - To unsubscri

Re: Sorting case insensitive wildcard query (with highlight)

2010-03-12 Thread Ian Lea
Can you just lowercase a dedicated sort field and leave the others alone. -- Ian. On Fri, Mar 12, 2010 at 10:47 AM, Kev Kilroy wrote: > > Hi, > > I'm using Lucene 2.4.1 with Hibernate Search 3.1.1. I have objects in the > index, for each field I index as follows: > > @Fields( value = { >    

Sorting case insensitive wildcard query (with highlight)

2010-03-12 Thread Kev Kilroy
Hi, I'm using Lucene 2.4.1 with Hibernate Search 3.1.1. I have objects in the index, for each field I index as follows: @Fields( value = { @Field(index = Index.TOKENIZED, store = Store.YES), @Field(name = "name_forSort", index = Index.UN_TOKENIZED, store = Store.NO), }) T

For a two word wildcard query like name:john s* , can I avoid expanding s* for the entire name field?

2010-02-04 Thread Melissa Hao
Hi, I am wondering about wildcard queries that are more than one word, such as: name:john s* Note: All terms are required (default boolean operator is AND). I know that for the query name:s* The s* is expanded over all s* terms in the name field. For the "john s*" case, is it possibl

Re: Wildcard query

2009-08-31 Thread Anshum
e word and then apply /expand the > wild card query. Is this a bug with queryparser? OR Analyzer will not stem > the word if it finds a wild card operator in it? > > Regards > Ganesh > > > - Original Message - > From: "Anshum" > To: > Sent: Mon

Re: Wildcard query

2009-08-31 Thread Ganesh
parser? OR Analyzer will not stem the word if it finds a wild card operator in it? Regards Ganesh - Original Message - From: "Anshum" To: Sent: Monday, August 31, 2009 3:01 PM Subject: Re: Wildcard query > Hi Ganesh, > > Its the snowball analyzer that uses English

Re: Wildcard query

2009-08-31 Thread Anshum
ywhere. Could you tell me what is the goal that is to be met here? I suppose using just the Snowball analyzer here might be enough for you and you might just give the wildcard query a complete skip. -- Anshum Gupta Naukri Labs! http://ai-cafe.blogspot.com The facts expressed here belong to ever

Wildcard query

2009-08-30 Thread Ganesh
Hello all, I am having some content with text "attention". If is search using "att*", "attent*", the results are displayed. If i search for "attenti*" then no results are displayed. I am using Snowball Analyzer for Indexing and Search (Lucene v2.4.1). Regards Ganesh Send instant messages to

Out of Memory Error while using WildCard Query

2009-01-01 Thread Ravichandra
le.com/Out-of-Memory-Error-while-using-WildCard-Query-tp21248743p21248743.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional co

Re: Wildcard query ...

2008-10-13 Thread Chris Hostetter
BooleanQuery picks a Scorer based on the number of clauses and what their options are ... all of teh scorers it might pick from are smart enough to continuously reorder the clauses having them "skip ahead" to the next document they match, beyond whatever docIds it already knows can't match (ba

Wildcard query ...

2008-10-08 Thread Dragon Fly
Let's say my index has two fields (Type and Description). Type is either 0 or 1 and Description is a string (up to 250 characters). I'd like to execute the following search: +Description:Honda* +Type:0 Would the query run faster if I specify the Type first: +Type:0 +Description:Honda

Re: lucene wildcard query with stop character

2008-06-16 Thread Chris Hostetter
: Hrm.. can we see a more specific example of the type of data you are trying to : query against here? As i understand the question, this is a fairly classic hierarchical organization of documents. Documents Foo>Bar>Baz and Foo>Bar>Bax are both children of Document Foo>Bar ... Foo>Barber is th

Re: lucene wildcard query with stop character

2008-06-12 Thread Matthew Hall
Hrm.. can we see a more specific example of the type of data you are trying to query against here? Matt Cam Bazz wrote: well the ? would work if the length of each token be same. however, instead of A>B>C I want tags that change dynamically from 1 to unlimited length. I just I could just pad

Re: lucene wildcard query with stop character

2008-06-12 Thread Cam Bazz
well the ? would work if the length of each token be same. however, instead of A>B>C I want tags that change dynamically from 1 to unlimited length. I just I could just pad every token to a normalized length such as ...000A but i am hoping there is a better method. if we could tell lucene

Re: lucene wildcard query with stop character

2008-06-12 Thread Matthew Hall
I assume you want all of your queries to function in this way? If so, you could just translate the * character into a ? at search time, which should give you the functionality you are asking for. Unless I'm missing something. Matt Cam Bazz wrote: Hello, Imagine I have the following documen

lucene wildcard query with stop character

2008-06-12 Thread Cam Bazz
Hello, Imagine I have the following documents having keys A A>B A>B>C A>B>D A>B>C>D now Imagine a query with keyword analyzer and a wildcard: A>B>* which will bring me A>B>C , A>B>D and A>B>C>D but I just want to get A>B>C and A>B>D so can I make a query like A>B>* but does not have the > cha

Re: multi-field and wildcard query highlighter questions

2007-07-26 Thread Lukas Vlcek
; > Hi, > > > > I have two questions: > > > > 1) Is it possible to get some highlighted text when using wildcard > > query? (I > > am using query rewrite) > > I found that it works for queries like [prefix*suffix] or > [prefix?suffix] > > but I was n

Re: multi-field and wildcard query highlighter questions

2007-07-20 Thread Mark Miller
document. Are you doing something weird with your TokenStream? - Mark Lukas Vlcek wrote: Hi, I have two questions: 1) Is it possible to get some highlighted text when using wildcard query? (I am using query rewrite) I found that it works for queries like [prefix*suffix] or [prefix?suffix] but

multi-field and wildcard query highlighter questions

2007-07-20 Thread Lukas Vlcek
Hi, I have two questions: 1) Is it possible to get some highlighted text when using wildcard query? (I am using query rewrite) I found that it works for queries like [prefix*suffix] or [prefix?suffix] but I was not able to get results for queries like [prefix*] 2) What kind of problems I

Re: Wildcard query with untokenized punctuation (again)

2007-06-15 Thread Erick Erickson
e- From: Mark Miller [mailto:[EMAIL PROTECTED] Sent: Thursday, June 14, 2007 12:07 PM To: java-user@lucene.apache.org Subject: Re: Wildcard query with untokenized punctuation (again) All depends on what you are looking for. Ill try and give a hint as to what is going on now: When the QueryPa

RE: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Renaud Waldura
his issue: how to get QueryParser to generate MultiPhraseQueries. Got some good ideas from it, but unfortunately no complete solution. I'll keep on hacking. --Renaud -Original Message- From: Mark Miller [mailto:[EMAIL PROTECTED] Sent: Thursday, June 14, 2007 12:07 PM To: java-user@

Re: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Mark Miller
e term smith and the wildcard query ann*, both with an occur of whatever your default operator is. One thing I am wondering is if you even really want the query to be a PhraseQuery or if your just accepting the behavior you getting from the QueryParser. Right now, PhraseQuery's do not support

RE: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Renaud Waldura
r [mailto:[EMAIL PROTECTED] Sent: Thursday, June 14, 2007 6:43 AM To: java-user@lucene.apache.org Subject: Re: Wildcard query with untokenized punctuation (again) Gotto agree with Erick here...best idea is just to preprocess the query before sending it to the QueryParser. My first thought i

Re: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Mark Miller
stock Lucene 2.0 query parser produces a PrefixQuery for the single token "smith,ann". This token doesn't exist in my index, and I don't get a match. I have found some references to this: http://www.nabble.com/Wildcard-query-with-untokenized-punctuation-tf3378386 . html but

Re: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Mathieu Lecarme
th,anna" and > "smith,annanicole". To find them, I enter the query <>. The > stock Lucene 2.0 query parser produces a PrefixQuery for the single token > "smith,ann". This token doesn't exist in my index, and I don't get a match. > > I have

Re: Wildcard query with untokenized punctuation (again)

2007-06-14 Thread Erick Erickson
,anna" and "smith,annanicole". To find them, I enter the query <>. The stock Lucene 2.0 query parser produces a PrefixQuery for the single token "smith,ann". This token doesn't exist in my index, and I don't get a match. I have found some references to this:

Re: Wildcard query with untokenized punctuation (again)

2007-06-13 Thread Mark Miller
that contained both "smith,anna" and "smith,annanicole". To find them, I enter the query <>. The stock Lucene 2.0 query parser produces a PrefixQuery for the single token "smith,ann". This token doesn't exist in my index, and I don't get a match. I

Wildcard query with untokenized punctuation (again)

2007-06-13 Thread Renaud Waldura
quot;smith,annanicole". To find them, I enter the query <>. The stock Lucene 2.0 query parser produces a PrefixQuery for the single token "smith,ann". This token doesn't exist in my index, and I don't get a match. I have found some references to this: http://www.nabble

RE: Wildcard query with untokenized punctuation

2007-03-12 Thread Chris Hostetter
: You're entirely correct about the analyzer (I'm using one that breaks on : non-alphanumeric characters, so all punctuation is ignored). To be : honest, I hadn't thought about altering this, but I guess I could; just : reticent that there might be unforeseen consequences. this is where the PerF

RE: Wildcard query with untokenized punctuation

2007-03-10 Thread Doron Cohen
reasoning behind not analyzing wildcard queries is also explained in the FAQ: "Are Wildcard, Prefix, and Fuzzy queries case sensitive?" Regards, Doron > > --Colin McGuigan > > -Original Message- > From: Doron Cohen [mailto:[EMAIL PROTECTED] > Sent: Saturday, Mar

RE: Wildcard query with untokenized punctuation

2007-03-10 Thread McGuigan, Colin
arch 10, 2007 2:08 AM To: java-user@lucene.apache.org Subject: Re: Wildcard query with untokenized punctuation Hi Colin, Is it possible that you are using an analyzer that breaks words on non letters? For instance SimpleAnalyzer? if so, the doc text: pagefile.sys is indexed as two words: pagefile

Re: Wildcard query with untokenized punctuation

2007-03-10 Thread Doron Cohen
Hi Colin, Is it possible that you are using an analyzer that breaks words on non letters? For instance SimpleAnalyzer? if so, the doc text: pagefile.sys is indexed as two words: pagefile sys At search time, the query text: pagefile.sys is also parsed-tokenized into a two words query: prof

RE: Wildcard query with untokenized punctuation

2007-03-09 Thread McGuigan, Colin
-Original Message- From: Steffen Heinrich [mailto:[EMAIL PROTECTED] Sent: Fri 3/9/2007 4:31 PM To: java-user@lucene.apache.org Subject: Re: Wildcard query with untokenized punctuation On 9 Mar 2007 at 15:10, McGuigan, Colin wrote: >> I have a "filename" field in Luc

Re: Wildcard query with untokenized punctuation

2007-03-09 Thread Steffen Heinrich
On 9 Mar 2007 at 15:10, McGuigan, Colin wrote: > I have a "filename" field in Lucene that holds a value, like this: > pagefile.sys > Hi Colin, I'm still _very_ new to lucene, but isn't that what the un-tokenized indexing is for? Like in 1.9.1 doc.add(Field.Keyword("filename", "pagefile.sys"));

Wildcard query with untokenized punctuation

2007-03-09 Thread McGuigan, Colin
(Lucene 1.9.1) I have a "filename" field in Lucene that holds a value, like this: pagefile.sys If I run searches through QueryParser, and I do a search for: pagefile.sys pagefile pagefile. This all works because it goes through getFieldQuery, which tokenizes the string and generat

Re: rewriting wildcard query before highlighting

2007-01-18 Thread Daniel Naber
On Thursday 18 January 2007 14:48, Mark Miller wrote: > Would it be more efficient to make a RAM index with just > the doc to be highlighted and then pass the reader of that into the > rewrite method before highlighting a query that expands? Yes, that's a valid approach, especially using MemoryIn

rewriting wildcard query before highlighting

2007-01-18 Thread Mark Miller
Looking for opinions: If I pass the reader of a large index to the query rewrite method just to highlight a single doc it seems the query I generate will expand to much more than I need. Would it be more efficient to make a RAM index with just the doc to be highlighted and then pass the reader of

Re: Leading wildcard query

2006-07-28 Thread Erick Erickson
You could form a filter, using the WildCardTermEnum or RegExTermEnum and then use the filter with a ConstantScoreQuery. You lose relevancy, but relevancy is an ambiguous concept with wildcards anyway. Using the query parser with a leading wildcard, even if enabled, is almost sure to give you a "T

Re: Leading wildcard query

2006-07-28 Thread Pravin Shinde
Thanx for reply Miles So, avoiding leading wildcard query was design decision for sake of efficiency. Thanx for information. On 7/28/06, Miles Barr <[EMAIL PROTECTED]> wrote: Pravin Shinde wrote: > I am trying to use Leading wildcard query, but I am not able to do it. > Any query

Re: Leading wildcard query

2006-07-28 Thread Miles Barr
Pravin Shinde wrote: I am trying to use Leading wildcard query, but I am not able to do it. Any query with leading wildcard is failing with lexical error. query = parser.parse( "*hi" ) JavaError: org.apache.lucene.queryParser.ParseException: Lexical error at line 1, column 1. E

Leading wildcard query

2006-07-28 Thread Pravin Shinde
Hi, I am trying to use Leading wildcard query, but I am not able to do it. Any query with leading wildcard is failing with lexical error. query = parser.parse( "*hi" ) JavaError: org.apache.lucene.queryParser.ParseException: Lexical error at line 1, column 1. Encountered: "

Wildcard query

2006-03-26 Thread D . Saravanaraj
Hi, I am performing wildcard query on the contents of the indexed documents. Using the extractTerms() method, i am extracting the terms which match the wildcard query. Since my index is of a large size, is it possible to get the top N terms which match the wildcard query. What is the ranking