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 > *To: *java-user@lucene.apache.org; > *Cc: *

'OR' search using Automaton query

I use automaton query to combine fuzzy and wildcard query.(for example a query on "*lucy*" should also return "*lucene*"). That's working great. Now, if I search for "*lucy Automaton query*", I want all the documents containing *lucene* or *Automaton* or *query* or *lucene Automaton* or *lucene qu

Non-index files under the search directory

Hello, I am trying to adding some meta data into the search data base. Instead of adding a new search filed or adding a phony document, I am looking at the method org.apache.lucene.store.Directory#createOutpu, which is create new file in the search directory. I am wondering does indexwriter can

Re: Understanding Query Parser Behavior

No Sent from my LG G4, an AT&T 4G LTE smartphone -- Original message--From: Peru RedmiDate: Mon, Nov 21, 2016 10:44 AMTo: java-user@lucene.apache.org;Cc: Subject:Understanding Query Parser Behavior Hello All ,Could someone explain *QueryParser* behavior on these cases1. While Indexing ,D

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