|
[
Permlink
| « Hide
]
Shay Banon added a comment - 12/Dec/08 02:38 PM
This was actually fixed in 2.1, can you give it a go? What I changed there is that I load the resource with no cache before getting the term frequencies. The main reason for the reload is that you can't really know which one loaded the resource (what reader, and what multi searcher, and which sub indexes this multi searcher was initialized with).
That definitely makes sense and sounds like it should fix this issue but it does appear to do so. I swapped out my M4 jar with the 2.1.0 and updated the lucene-core.jar I was using to match 2.1.0, and I get the same result (EOF).
Stack trace: Exception in thread "main" org.compass.core.engine.SearchEngineException: Failed to fetch term info for resource [{a2} stored/uncompressed,indexed,omitNorms<$/uid:a2#1#>,[stored/uncompressed,indexed,omitNorms<alias:a2>],[stored/uncompressed,indexed<id:1>],[stored/uncompressed,indexed,tokenized,termVector<value1:test1>],[stored/uncompressed,indexed,tokenized,termVector<value2:test2>]]; nested exception is java.io.IOException: read past EOF java.io.IOException: read past EOF at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:151) at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:38) at org.apache.lucene.store.IndexInput.readInt(IndexInput.java:68) at org.apache.lucene.store.IndexInput.readLong(IndexInput.java:91) at org.apache.lucene.index.TermVectorsReader.get(TermVectorsReader.java:345) at org.apache.lucene.index.SegmentReader.getTermFreqVectors(SegmentReader.java:1059) at org.apache.lucene.index.MultiReader.getTermFreqVectors(MultiReader.java:169) at org.compass.core.lucene.util.LuceneHelper.getTermFreqVectors(LuceneHelper.java:192) ... Sorry, I missed the getTermFreqVectors and only did it for getTermFreqVector in 2.1. I already fixed it a few weeks ago for both 2.1.1 and 2.2.0 M1. I will release 2.1.1 next week. You can try the 2.1 nightly build to test that it solves the problem.
Sorry for the late reply but I was on holiday. I downloaded a 2.1.1 build and it does indeed resolve the issue. Do you know when this release will be available?
Thanks! I will release it either this this weeked.
|
||||||||||||||||||||||||||||||||||||||||||