search

dileepajayakody / semanticvectors

Automatically exported from code.google.com/p/semanticvectors
Other
1 stars 0 forks source link

SV 1.30 incompatible with Lucene 3.0.3. #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Semantic Vectors does not appear to work with Lucene 3.0.3.

See 
http://groups.google.com/group/semanticvectors/browse_thread/thread/35c3e9a16a9e
4acc?hl=en_US#
 and http://groups.google.com/group/semanticvectors/browse_thread/thread/fb250cfc5528e4aa?hl=en_US#

Original issue reported on code.google.com by widd...@google.com on 9 Dec 2010 at 8:44

GoogleCodeExporter commented 9 years ago 
I think I know where this problem comes from. Is anyone already working on this?

Original comment by johann.petrak@gmail.com on 9 Dec 2010 at 10:08

GoogleCodeExporter commented 9 years ago 
I'm not looking at it right now, but it seems like a mixup between a file 
descriptor and a filesystem path. BuildIndex line 158 (in the stack dump) comes 
right after deciding that the docvector is "inmemory", which further supports 
the file descriptor theory. But I'm not looking at it right now, maybe in the 
coming days if I get time.

Original comment by ThomasCR...@gmail.com on 9 Dec 2010 at 10:27

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Checked in a fix for this as of revision 431.
This was casued by IndexReader.directory().toString() returning something 
different than before making the replaceAll method for determining the actual 
directory path in class DocVectors not work any more. Replaced it with 
something that works in lucene 3.0.2 and 3.0.3.

Original comment by johann.petrak@gmail.com on 9 Dec 2010 at 10:37

GoogleCodeExporter commented 9 years ago

Original comment by johann.petrak@gmail.com on 9 Dec 2010 at 10:38