Re: Understanding Query Parser Behavior

Hello , It would be great , if someone could help on this. *Note : I am using Lucene 4.10.4 version* On Mon, Nov 28, 2016 at 5:37 PM, Peru Redmi wrote: > Any help on this would be greatly appreciated. > > Thanks. > > On Thu, Nov 24, 2016 at 8:14 PM, Peru Redmi wrote: >

Re: Understanding Query Parser Behavior

Any help on this would be greatly appreciated. Thanks. On Thu, Nov 24, 2016 at 8:14 PM, Peru Redmi wrote: > > Hello Mike, > > Here is, how i analyze my text using QueryParser ( with ClassicAnalyzer) > and plain ClassicAnalyzer. On checking the same in luke, i get "//"

Re: Understanding Query Parser Behavior

M, Michael McCandless < luc...@mikemccandless.com> wrote: > Hi, > > You should double check which analyzer you are using during indexing. > > The same analyzer on the same string should produce the same tokens. > > Mike McCandless > > http://blog.mikemccandless.com

Re: Understanding Query Parser Behavior

Could someone elaborate this. On Tue, Nov 22, 2016 at 11:41 AM, Peru Redmi wrote: > Hello, > Can you help me out on your "No" . > > On Mon, Nov 21, 2016 at 11:16 PM, wmartin...@gmail.com < > wmartin...@gmail.com> wrote: > >> No >> &g

Re: Understanding Query Parser Behavior

Hello, Can you help me out on your "No" . On Mon, Nov 21, 2016 at 11:16 PM, wmartin...@gmail.com wrote: > No > > Sent from my LG G4, an AT&T 4G LTE smartphone > > -- Original message-- > *From: *Peru Redmi > *Date: *Mon, Nov 21, 2016 10:44 AM > *T

Understanding Query Parser Behavior

Hello All , Could someone explain *QueryParser* behavior on these cases 1. While Indexing , Document doc = new Document(); doc.add(new Field("*Field*", "*http://www.google.com *", Field.Store.YES, Field.Index.ANALYZED)); index has *two* terms - *http* & *www.googl