RE: KeywordAnalyzer still getting tokenized on spaces

2014-09-09 Thread Milind
"matchQuery" and is in most > cases the approach you should use, if you don't need "syntax". > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > > -Origina

RE: KeywordAnalyzer still getting tokenized on spaces

2014-09-09 Thread Uwe Schindler
eptember 09, 2014 9:37 AM > To: java-user@lucene.apache.org > Subject: Re: KeywordAnalyzer still getting tokenized on spaces > > The result of QueryParser is confusing. The problem is that you assume the > query parser uses the analyzer to parse your query. However, that is not the > case

Re: KeywordAnalyzer still getting tokenized on spaces

2014-09-09 Thread atawfik
The result of QueryParser is confusing. The problem is that you assume the query parser uses the analyzer to parse your query. However, that is not the case. The query parser first parses the query string, then applies the analyzer. In other words, the query parser will split the query string usin

Re: KeywordAnalyzer and Boosting

2010-11-18 Thread Pulkit Singhal
Thanks Ian, Yup that would do the trick for me, it seems. Also I would like to say that the following also worked, I only realized it after I went through the scores coming from my results step by step: KeywordAnalyzer + Index.ANALYZED (index-time norms were present) Cheers! On Thu, Nov 18, 20

Re: KeywordAnalyzer and Boosting

2010-11-18 Thread Ian Lea
Have you tried explicitly setting norms on/off the way you want with Field.setOmitNorms(boolean)? -- Ian. On Thu, Nov 18, 2010 at 12:54 AM, Pulkit Singhal wrote: > Based on my experimentation and what it says in the Lucene 2nd edition book: > "Using a KeywordAnalyzer on special fields during in

Re: KeywordAnalyzer and Boosting

2010-11-17 Thread Pulkit Singhal
Based on my experimentation and what it says in the Lucene 2nd edition book: "Using a KeywordAnalyzer on special fields during indexing would eliminate the use of Index.NOT_ANALYZED_NO_NORMS during indexing and replace it with Index.ANALYZED." I guess that there is no way to use KeywordAnalyzer du

Re: KeywordAnalyzer

2009-07-01 Thread Simon Willnauer
Hi there, On Wed, Jul 1, 2009 at 7:52 PM, John Seer wrote: > > Hi, > > I have docs in my index like: > > name: open & close > name water fall\ > name: play-end-go > > I am using KeywordAnalyzer to index docs and for querying > > term: play-end-go > > Query qp= new QueryParser("name", new KeywordAn

Re: KeywordAnalyzer

2009-07-01 Thread John Seer
Hi, I have docs in my index like: name: open & close name water fall\ name: play-end-go I am using KeywordAnalyzer to index docs and for querying term: play-end-go Query qp= new QueryParser("name", new KeywordAnalyzer()).parse(term); After I am doing this I am getting error about - and if m

Re: KeywordAnalyzer

2009-07-01 Thread Simon Willnauer
On Wed, Jul 1, 2009 at 7:27 PM, John Seer wrote: > > Hello, > I am using KeywordAnalyzer for one of the fields and have problem with it. > When my original term has not English characters as well as - &  \  /. What are you problems? Can you elaborate this a little :) > Is there any alternative for

Re: KeywordAnalyzer vs. Field.Index.UN_TOKENIZED

2007-05-24 Thread Steven Rowe
Hi Terry, The one place I know where KeywordAnalyzer is definitely useful is when it is used in conjunction with PerFieldAnalyzerWrapper. Steve dontspamterry wrote: > Hi Otis, > > I tried both ways, did some queries, and results are the same, so I guess > it's a matter of preference??? > > -Te

Re: KeywordAnalyzer vs. Field.Index.UN_TOKENIZED

2007-05-24 Thread dontspamterry
Hi Otis, I tried both ways, did some queries, and results are the same, so I guess it's a matter of preference??? -Terry Otis Gospodnetic wrote: > > Terry, > I think you are right. Just use UN_TOKENIZED, that will do what you need. > > Otis > . . . . . . . . . . . . . . . . . . . . . . . .

Re: KeywordAnalyzer vs. Field.Index.UN_TOKENIZED

2007-05-24 Thread Otis Gospodnetic
Terry, I think you are right. Just use UN_TOKENIZED, that will do what you need. Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ - Tag - Search - Share - Original Message From: dontspamterry <[EMAIL PROTECTED]> To: java-user@lucene.