John X wrote:
One thorny issue is: how to deal with various FetcherOutput states. Before parsing was separated from fetching, failed parsing was logged as NOT_FOUND. Now it will be marked as CANT_PARSE. We may have to increase VERSION in FetcherOutput from 4 to 5, so that "old" ./fetcher can be easily distignushed from new ./fetcher and ./fetcher_output. I did not do that because not feel compelled at that time.
Or we could treat the old behaviour as a bug, and not increase the version number... Normally, the version number in all Writable's is related to specific disk layout of the content, and not the content's interpretation. In other words, I think we don't have to increase the version number.
-- Best regards, Andrzej Bialecki
------------------------------------------------- Software Architect, System Integration Specialist CEN/ISSS EC Workshop, ECIMF project chair EU FP6 E-Commerce Expert/Evaluator ------------------------------------------------- FreeBSD developer (http://www.freebsd.org)
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
