sual for scp to corrupt the copy unless something
catastrophic happens (eg disk full, disk is bad, RAM is bad, etc.).
Mike
crspan wrote:
Thanks so much, Mike. Those runtime errors were caused by one
corrupted index, somehow corrupted during scp. It has Nothing to do
with lucene 2.3.2.
For th
Thanks so much, Mike. Those runtime errors were caused by one corrupted
index, somehow corrupted during scp. It has Nothing to do with lucene 2.3.2.
For those who come by this thread:
Please "CheckIndex"
That would saved me many hours of fruitless debugging.
Cheers,
Charlie
Michael M
-- OS: Linux lg99 2.6.5-7.276-smp #1 SMP Fri Sep 28 20:33:22 AKDT 2007
x86_64 x86_64 x86_64 GNU/Linux
-- Lucene: 2.3.2 (tried 2.2.0 as well, since the index was built
around 2.2.0, jdk1.6.0_01 )
-- JDK: Sun jdk1.6.0_06 ( from jdk-6u6-linux-x64.bin ) & Sun
jdk1.5.0_15 ( from jdk-1_5_0_
coincidence or it is from 2.3.2 ?
env:
lucene 2.3.2
jdk1.6.0_06 & jdk1.5.0_15
QueryString:
illeg^30.820824 technolog^22.290413 transfer^33.307804
Error: java.lang.ArrayIndexOutOfBoundsException:
132704java.lang.ArrayIndexOutOfBoundsException: 132704
at
org.apache.lucene.search.BooleanScorer2$
ie
Otis Gospodnetic wrote:
Use KeywordAnalyzer to leave "U.S." as-is and index it as-is.
Otis
--
Lucene Consulting -- http://lucene-consulting.com/
- Original Message
From: crspan <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Saturday, July 14, 2007 5:1
Would you please advice the best practice of indexing:
U.S.
The standard analyzer will transform it to be "us", which collide with
"us"(we).
Thanks,
Charlie
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com