> But the fix seems to be included in 1.4.2.
> see
> http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.96.2.4
> item 5
Thank you! I'm just downloading 1.4.2.
I hope it'll work ;)
Sanyi
__
Do you Yahoo!?
Check out t
Sanyi writes:
> Thanx for your replies guys.
>
> Now, I was trying to locate the latest patch for this "problem group", and
> the last thread I've
> read about this is:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=25820
> It ends with an open question from Morus:
> "If you want me to chang
Thanx for your replies guys.
Now, I was trying to locate the latest patch for this "problem group", and the
last thread I've
read about this is:
http://issues.apache.org/bugzilla/show_bug.cgi?id=25820
It ends with an open question from Morus:
"If you want me to change the patch, let me know. That
Sanyi writes:
>
> This query works as expected:
> validword AND stopword
> (throws out the stopword part and searches for validword)
>
> This query seems to crash:
> stopword AND validword
> (java.lang.ArrayIndexOutOfBoundsException: -1)
>
> Maybe it can't handle the case if it had to remove the
On Wednesday 10 November 2004 10:46, Sanyi wrote:
> This query seems to crash:
> stopword AND validword
> (java.lang.ArrayIndexOutOfBoundsException: -1)
I think this has been fixed in the development version (which will become
Lucene 1.9).
Regards
Daniel
--
http://www.danielnaber.de
---
Hi!
I've left out custom stopwords from my index using the
StopAnalyzer(customstopwords).
Now, when I try to searh the index the same way
(StopAnalyzer(customstopwords)), it seems to act
strange:
This query works as expected:
validword AND stopword
(throws out the stopword part and searches for
