Re: ComplexPhraseQueryParser with wildcards

2017-01-02 Thread Mikhail Khludnev
https://issues.apache.org/jira/browse/LUCENE-7614 is raised. On Tue, Dec 20, 2016 at 4:55 PM, Otmar Caduff wrote: > Hi, > > I have an index with a single document with a field "field" and textual > content "johnny peters" and I am using > org.apache.lucene.queryparser.complexPhrase.ComplexPhrase

Re: ComplexPhraseQueryParser with wildcards

2016-12-20 Thread Mikhail Khludnev
It probably deserves a jira, although it's minor. On Tue, Dec 20, 2016 at 6:18 PM, Otmar Caduff wrote: > Thanks for your response, Ahmet! > > I agree, a meaningful phrase query should have at least two terms. However, > why should the query "john" (without wildcard) then work? > > I'm trying to

Re: ComplexPhraseQueryParser with wildcards

2016-12-20 Thread Otmar Caduff
Thanks for your response, Ahmet! I agree, a meaningful phrase query should have at least two terms. However, why should the query "john" (without wildcard) then work? I'm trying to figure out if I can use ComplexPhraseQueryParser as a default in my application or if I have to handle some cases di

Re: ComplexPhraseQueryParser with wildcards

2016-12-20 Thread Ahmet Arslan
Hi Otmar, A single term inside quotes is meaningless. A phrase query should have at least two terms in it, shouldn't it? What is your intention with a such "john*" query? Ahmet On Tuesday, December 20, 2016 4:56 PM, Otmar Caduff wrote: Hi, I have an index with a single document with a fi

ComplexPhraseQueryParser with wildcards

2016-12-20 Thread Otmar Caduff
Hi, I have an index with a single document with a field "field" and textual content "johnny peters" and I am using org.apache.lucene.queryparser.complexPhrase.ComplexPhraseQueryParser to parse the query: field: (john* peter) When searching with this query, I am getting the document as expected.