2010/8/11 Veit Jahns <nuncupa...@googlemail.com>: > 2010/8/11 Kostka Bořivoj <kos...@tovek.cz>: >>> > 2) MockRAMDirectory::close always throws an exception because >>> > segments.gen is in list of open files, no idea if this is a bug in >>> > RAMDirectory or MockRAMDirectory >>> >>> Why do you use MockRAMDirectory here? I ported this class from JLucene, >>> because I >>> needed once a directory implementation that intentionally throws >>> exceptions. And >>> because the close-methods of RAMDirectory and MockRAMDirectory are >>> identical to >>> the JLucene methods, I'd say that's neither a bug of RAMDirectory nor >>> MockRAMDirectory. >> >> I use MockRAMDirectory just because it is used in original java test I >> ported. It is used >> in many tests in test/index folder so I wanted to test MockRAMDirectory >> itself before >> using it in other tests. > > You are right. Something is odd there. I will take a close look tomorrow.
The Bug seems to be in SegmentInfos.cpp. In some case the open generation file will not be closed (diff attached). Veit
SegmentInfos.cpp.diff
Description: Binary data
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ CLucene-developers mailing list CLucene-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clucene-developers
