-
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>> > -Original Message-
>> > From: Rohit Banga [mailto:iamrohitba...@gmail.com]
>> > Sent: Tuesday, February 09, 2
aphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Rohit Banga [mailto:iamrohitba...@gmail.com]
> > Sent: Tuesday, February 09, 2010 9:03 AM
> > To: java-user@lucene.apache.org
> > Subject: Re: Lucene fields not analyzed
> >
> >
.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Rohit Banga [mailto:iamrohitba...@gmail.com]
> Sent: Tuesday, February 09, 2010 9:03 AM
> To: java-user@lucene.apache.org
> Subject: Re: Lucene fields not ana
Use Luke.
It can show you the index contents and your parsed query and should show what
is breaking down here.
On 9 Feb 2010, at 08:03, Rohit Banga wrote:
> let us assume this is the only field that is relevant (others are stored and
> not indexed).
> i tried termquery and it does not work.
> i
let us assume this is the only field that is relevant (others are stored and
not indexed).
i tried termquery and it does not work.
i also tried keyword analyzer and still could not make it work.
@Mark
i cannot escape the spaces in my query as i am using Lucene to identify
occurences of names among
I suspect it is because QueryParser uses space characters to separate different
clauses in a query string while you want the space to represent some content in
your "name" field. Try escaping the space character.
Cheers
Mark
On 9 Feb 2010, at 07:26, Rohit Banga wrote:
> Hello
>
> i have a f
QueryParser uses the given Analyzer when constructing they query, so it will
never hit a NOT_ANALYZED term. In general, it is a bad idea to use QueryParser
on fields that are not analyzed. There are two possibilities to solve the
problem:
- Instantiate the query to match the not-analyzed (but i
