Re: Migration to Lucene 6.x

Hi In Lucene 3.x, for search word with special characters, phrase query is formed. For eg: For input *google-chrome-stable*, query formed as "google chrome stable". But in Lucene 6.x, I can't achieve this. Is there any way to achieve it? On Mon, Jul 31, 2017 at 2:53

Re: Migration to Lucene 6.x

7 at 2:50 PM, krish mohan wrote: > Hi >I'm using Lucene 4.10.4. QueryParser in LUCENE_30 forms phrase query > for input with special characers ($,/,-,...) > >For eg: > For input *google-chrome-stable*, query formed as "google chrome > stable

Migration to Lucene 6.x

Hi I'm using Lucene 4.10.4. QueryParser in LUCENE_30 forms phrase query for input with special characers ($,/,-,...) For eg: For input *google-chrome-stable*, query formed as "google chrome stable". Using QueryParser(Version matchVersion, String f, Analyzer a)

AnalyzingInfixSuggestor and PrefixQuery performance difference

hi, When using AnalyzingInfixSuggestor, the suggest performance is faster than the prefix query. How AnalyzingInfixSuggestor is faster than prefixQuery? Is FST constructed in different way for AnalyzingInfixSuggestor? Or any other reason? Thanks.

How FST constructed in lucene?

During search, whether Lucene uses FST in .tip file to match against the terms? How the changes to the index will be updated in FST? Will it be re-constructed or will it be updated in existing FST? In case of wildcard and fuzzy queries, Lucene needs to test a large number of terms. Will FST be use

Search optimization - regd

Hi.. I am building a search for my application. For the entered search term (foo), 1) I look for exact match (foo), if it returns NULL 2) I use fuzzy search (foo~), if it returns NULL 3) I use wildcard (foo*). Is this an efficient way? Or is there any lucene method to do all these? Thanks.