DO NOT REPLY [Bug 34570] - A new Greek Analyzer for Lucene

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Fwd: Lucene and Groovy...

Erik Hatcher wrote: There are two .java files attached that may not make it through to the list. These are simple wrappers that do exactly what you'd expect. The idea is to make dealing with Lucene Hits more "Java like" with an Iterator, which in turn makes this much more amenable to Groovy. +

DO NOT REPLY [Bug 31841] - [PATCH] MultiSearcher problems with Similarity.docFreq()

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Lucene and Groovy...

On Apr 25, 2005, at 2:56 PM, Doug Cutting wrote: Erik Hatcher wrote: There are two .java files attached that may not make it through to the list. These are simple wrappers that do exactly what you'd expect. The idea is to make dealing with Lucene Hits more "Java like" with an Iterator, which i

DO NOT REPLY [Bug 34570] - A new Greek Analyzer for Lucene

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

HighlighterTest failure

I get a failure running HighlighterTest from the Subversion trunk. Below are the details. What's the fix? Thanks, Erik [junit] Searching for: multi* [junit] - --- [junit] Testcase: testMultiSearcher(org.apache.lucene.search.highligh

DO NOT REPLY [Bug 34585] - Contributing a High-performance single-document main memory Apache Lucene fulltext search index.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34585] - Contributing a High-performance single-document main memory Apache Lucene fulltext search index.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34585] - Contributing a High-performance single-document main memory Apache Lucene fulltext search index.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: HighlighterTest failure

Erik Hatcher wrote: I get a failure running HighlighterTest from the Subversion trunk. Below are the details. What's the fix? I don't have the code here to run, but the problem is that MultiSearcher.rewrite(line 298) is calling Query.combine, which requires all the combined queries to be equal.

Re: svn commit: r164695 - in /lucene/java/trunk: CHANGES.txt src/java/org/apache/lucene/search/Hit.java src/java/org/apache/lucene/search/HitIterator.java src/java/org/apache/lucene/search/Hits.java s

Hello, Would it be better to explicitly check for out of bounds hitNumber instead of catching ArrayIndexOutOfBoundsException? if (hitNumber > hits.length()) { throw new NoSuchElementException(); } Also, is "a future for a hit" a typo, or does that actually mean something? This makes me think

SortTest failing

Hm, Erik is not alone with unit tests failing. My HighlighterTest passes (I didn't do svn update today yet), but I see SortTest failing: [junit] Testcase: testNormalizedScores(org.apache.lucene.search.TestSort): FAILED [junit] expected:<0.375> but was:<0.392445> [junit] junit.framewo

Re: SortTest failing

Otis Gospodnetic wrote: Hm, Erik is not alone with unit tests failing. My HighlighterTest passes (I didn't do svn update today yet), but I see SortTest failing: [junit] Testcase: testNormalizedScores(org.apache.lucene.search.TestSort): FAILED [junit] expected:<0.375> but was:<0.392445> [

Re: svn commit: r164695 - in /lucene/java/trunk: CHANGES.txt src/java/org/apache/lucene/search/Hit.java src/java/org/apache/lucene/search/HitIterator.java src/java/org/apache/lucene/search/Hits.java s

On Apr 25, 2005, at 10:36 PM, Otis Gospodnetic wrote: Would it be better to explicitly check for out of bounds hitNumber instead of catching ArrayIndexOutOfBoundsException? if (hitNumber > hits.length()) { throw new NoSuchElementException(); } Good eye. I've added a test case that identified thi

Re: SortTest failing

On Apr 25, 2005, at 10:55 PM, Otis Gospodnetic wrote: Hm, Erik is not alone with unit tests failing. My HighlighterTest passes (I didn't do svn update today yet) Let me know what happens after you fully update and build the main Lucene JAR, then run the highlighter build. , but I see SortTest fa

Re: HighlighterTest failure

On Apr 25, 2005, at 10:02 PM, Chuck Williams wrote: Erik Hatcher wrote: I get a failure running HighlighterTest from the Subversion trunk. Below are the details. What's the fix? I don't have the code here to run, but the problem is that MultiSearcher.rewrite(line 298) is calling Query.combine, w

Re: HighlighterTest failure

Erik Hatcher wrote: On Apr 25, 2005, at 10:02 PM, Chuck Williams wrote: Erik Hatcher wrote: I get a failure running HighlighterTest from the Subversion trunk. Below are the details. What's the fix? I don't have the code here to run, but the problem is that MultiSearcher.rewrite(line 298) is cal