Yeah, that's the symptom of missing index.I thought i'd fixed this some time ago. One still might get an when iterating through entries from a truncated segment, but no longer when opening it. So it should always be possible to read all the entries that were flushed: an index file should always be present, and EOF on the index file should be trapped, generating only a warning.
You are right - I checked the code once again. There should only be a warning, unless the index file was missing. But in that case there is an IOException thrown, not an EOFException - perhaps Stefan had this in mind...
I notice this problem a long time ago, sorry I notice that this was already solved! I'm not up to date. :-(
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Nutch-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-general
