Re: Boolean Query not working in Lucene 4.0

Try detailing both your expected behavior and the actual behavior. Try providing an actual code snippet and actual index and query data. Is it failing for all types and titles or just for some? -- Jack Krupansky -Original Message- From: saisantoshi Sent: Tuesday, February 26, 2013 6:

RE: Searching for keywords .net,c#,...

: which seems to override incrementToken() ( guess as I don't know java ) : however using lucene.net 3.0.3, I can override Lucene.Net is a completely seperate project from Lucene, with it's own APIs, release cycles, and user community. Your best bet at getting help from people who are familiar

Boolean Query not working in Lucene 4.0

The following query does not seems to work after we upgrade from 2.4 - 4.0 *+type:sometype +title:sometitle** Any ideas as to what are some of the places to look for? Is the above Query correct in syntax. Appreciate if you could advise on the above? Thanks, Sai. -- View this message in contex

Re: Uable to extends TopTermsRewrite in Lucene 4.1

On 26/02/2013 17:22, Uwe Schindler wrote: Hi, You cannot override rewrite() because you could easily break the logic behind TopTermsRewrite. If you want another behavior, subclass another base class and wrap the TopTermsRewrite instead of subclassing it (the generics also enforce that the rewrit

RE: Uable to extends TopTermsRewrite in Lucene 4.1

> Hi, > > You cannot override rewrite() because you could easily break the logic > behind TopTermsRewrite. If you want another behavior, subclass another > base class and wrap the TopTermsRewrite instead of subclassing it (the > generics also enforce that the rewrite needs to rewrite() to a class

RE: Uable to extends TopTermsRewrite in Lucene 4.1

Hi, You cannot override rewrite() because you could easily break the logic behind TopTermsRewrite. If you want another behavior, subclass another base class and wrap the TopTermsRewrite instead of subclassing it (the generics also enforce that the rewrite needs to rewrite() to a class that’s sp

Uable to extends TopTermsRewrite in Lucene 4.1

In Lucene 3.6 I had code that replicated a Dismax Query, and the search used fuzzy queries in some cases to match values. But I was finding the score attributed to matches on fuzzy searches was completely different to the score attributed to matches on exact searches so the total score returned

In Lucene 4.1 FuzzyQuery constructor now takes parameter maxEdits instead of parameter minSimilarity

FuzzyQuery constructor now takes parameter maxEdits instead of parameter minSimilarity. But I'm unclear how to map from the old value to the new value or whether they are unrelated and can no longer be compared. I was previously using a minsimilarity of 0.5f thanks Paul --

Re: NullPointerException thrown on tokenizer in 4.1, worked okay in 3.6

On 26/02/2013 12:29, Paul Taylor wrote: This code worked in 3.6 but now throws nullpointer exception in 41, Im not expecting there to be a token created, but surely it shouldn't throw NullPointerException Tokenizer tokenizer = new org.apache.lucene.analysis.standard.StandardTokenizer(Version.

Re: ArrayIndexOutOfBoundsException trying to use tokenizer in Lucene 4.1

On 26/02/2013 13:29, Alan Woodward wrote: Hi Paul, You need to call tokenizer.reset() before you call incrementToken() Alan Woodward www.flax.co.uk Hi, thanks that fixes it

Re: ArrayIndexOutOfBoundsException trying to use tokenizer in Lucene 4.1

Hi Paul, You need to call tokenizer.reset() before you call incrementToken() Alan Woodward www.flax.co.uk On 26 Feb 2013, at 12:26, Paul Taylor wrote: > This works in 3.6, but in 4.1 fails whats wrong with the code > > public void testTokenization() throws IOException >{ >StringBu

NullPointerException thrown on tokenizer in 4.1, worked okay in 3.6

This code worked in 3.6 but now throws nullpointer exception in 41, Im not expecting there to be a token created, but surely it shouldn't throw NullPointerException Tokenizer tokenizer = new org.apache.lucene.analysis.standard.StandardTokenizer(Version.LUCENE_41, new StringReader("!!!")); to

ArrayIndexOutOfBoundsException trying to use tokenizer in Lucene 4.1

This works in 3.6, but in 4.1 fails whats wrong with the code public void testTokenization() throws IOException { StringBuffer sb = new StringBuffer(); for(char i=0;i<100;i++) { Character c = new Character(i); if(!Character.isWhitespace(c)) {

Re: What replaces the computeNorm method in DefaultSimilarity in 4.1 now that the method is final

On 19/02/2013 11:42, Paul Taylor wrote: What replaces the computeNorm method in DefaultSimilarity in 4.1 Ive always subclassed DefaultSimilarity to resolve an issue whereby when document has multiple values in a field (because has one-many relationship) its score worse then a document which ju

Re: Not getting matches for analyzers using CharMappingFilter with Lucene 4.1

On 25/02/2013 11:24, Thomas Matthijs wrote: On Mon, Feb 25, 2013 at 12:19 PM, Thomas Matthijs > wrote: On Mon, Feb 25, 2013 at 11:30 AM, Thomas Matthijs mailto:li...@selckin.be>> wrote: On Mon, Feb 25, 2013 at 11:24 AM, Paul Taylor mailto:paul_t