Re: fuzzy search and distance tilde

2024-08-20 Thread Greg Huber
(like TermQuery, PhraseQuery,). Finally combine the different queries constructed with BooleanQuery together and pass the complex result to IndexSearcher. For programmatic query construction the Query subclasses are the way to go. Uwe Am 11.08.2024 um 10:37 schrieb Greg Huber: Looking through my h

Re: fuzzy search and distance tilde

2024-08-14 Thread Greg Huber
) { } As we all know, hacks often start with exceptions from fishing.  There have been alot of fishing queries as of late. On 13/08/2024 20:08, Mikhail Khludnev wrote: On Sun, Aug 11, 2024 at 11:38 AM Greg Huber wrote: Is there a way to escape these or configure lecene just to return no

fuzzy search and distance tilde

2024-08-11 Thread Greg Huber
Looking through my httpd logs I see lots of searches as such /devbox/search?q=%29%20AND%203318%3D4385%20AND%20%287778%3D7778 ie : ) AND 3318=4385 AND (7778=7778 guess they might be fishing for something. For the fuzzy search I use a different distance values and the default is  ~0.6 String

fuzzy search with multiple terms

2021-02-27 Thread Greg Huber
Hello, I am trying to get a fuzzy search to work, maybe I am not understanding how it is supposed to work, can someone put me in the right direction?  It seems to be always doing an OR when I use BooleanClause.Occur.MUST (for loop).  Latest version of lucene. eg for a term stone brick is i

AnalyzingInfixSuggester suggest apostrophe

2019-12-23 Thread Greg Huber
Hello, I am using the AnalyzingInfixSuggester for my suggester, and trying to get the apostrophe to work correctly (highlighter and search). I am adding a field to my main index for the suggester with the apostrophe included: document.add(new StoredField(FieldConstants.C_DESCRIPTION_SUGGES

Re: AnalyzingInfixSuggester

2018-02-24 Thread Greg Huber
I build org.apache.lucene.analysis.Analyzer using these options and the suggester works 100% for me. return CustomAnalyzer.builder() .withTokenizer(StandardTokenizerFactory.class) .addTokenFilter(StandardFilterFactory.class) .addTokenFilt

Re: Strange results returned from suggester

2017-01-29 Thread Greg Huber
ene.apache.org/core/6_4_0/analyzers-common/org/ > apache/lucene/analysis/custom/CustomAnalyzer.html > > Uwe > > - > Uwe Schindler > Achterdiek 19, D-28357 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > Fr

Re: Strange results returned from suggester

2017-01-29 Thread Greg Huber
cCandless [mailto:luc...@mikemccandless.com] > > Sent: Sunday, January 29, 2017 12:28 PM > > To: Greg Huber ; Lucene Users > u...@lucene.apache.org> > > Subject: Re: Strange results returned from suggester > > > > That's right, just make your own analyzer, forke

Re: Strange results returned from suggester

2017-01-29 Thread Greg Huber
components in an analyzers) is > normal practice... > > Mike McCandless > > http://blog.mikemccandless.com > > > On Sat, Jan 28, 2017 at 6:09 AM, Greg Huber wrote: > > Michael, > > > > Thanks for the update, so I just duplicate StandardAnalyzer and rep

Re: Strange results returned from suggester

2017-01-28 Thread Greg Huber
ster with an analyzer, and your analysis > chain includes a StopFilter and "will" is a stop word? > > Mike McCandless > > http://blog.mikemccandless.com > > > On Fri, Jan 27, 2017 at 10:42 AM, Greg Huber wrote: > > Hello, > > > > Is there anywa

Strange results returned from suggester

2017-01-27 Thread Greg Huber
Hello, Is there anyway to see why items are returned from the suggester? Similar to the search. I have a really strange case where if I enter 'will' (without the quotes) it seems to return all the search results. example: there should be two entries beginning with will* ie william and Willoug

Re: Depreciated IntField field in v6

2016-04-15 Thread Greg Huber
Thanks, guess I should have been using StoredField in the firstplace! document.add(new StoredField(FieldConstants.LUCENE_WEIGHT_LINES, catalogue.getSearchWeight())); On 15 April 2016 at 17:40, Robert Muir wrote: > On Fri, Apr 15, 2016 at 11:48 AM, Greg Huber wrote: > > Hello, >

Depreciated IntField field in v6

2016-04-15 Thread Greg Huber
Hello, I was using the IntField field to set the weight on my suggester. (LegacyIntField works) old: document.add(new IntField( FieldConstants.LUCENE_WEIGHT_LINES, catalogue.getSearchWeight(), Field.Store.YES)); I tried to use the IntPoint but it does not seem to work: new:

AnalyzingInfixSuggester Lucene 5.3.0

2015-08-24 Thread Greg Huber
Hello, I am extending AnalyzingInfixSuggester for use with my suggester where I change the query to be a AND rather than an OR in the finishQuery(..) method. ie /** * Subclass can override this to tweak the Query before searching. */ protected Query finishQuery(Builder in, boolean

version 4.10.3 AnalyzingInfixSuggester with multiple contexts

2015-01-09 Thread Greg Huber
Hello, I am trying to use multiple contexts on the org.apache.lucene.search.suggest.analyzing.AnalyzingInfixSuggester but there is a mistake on the CONTEXTS_FIELD_NAME, the BooleanClause.Occur.SHOULD needs to be BooleanClause.Occur.MUST. ( see << below) I noticed that its been fix