Hi lewis, Since current updatedb job does not accommodate batchId field, so it will trigger many problems. For example, I try to crawl one URL(only one URL in the DB) by crawl command with -depth 3. And the default fetch interval = 7 days. In every crawling cycle of updatedb job, the fetch time of the url will be added 7 days. Thus, the final fetch time of this initial url will be added 7 * 3 days. Without batchId field, updatedb job will add fetch interval to every url in the DB no matter whether it is fetched in the same cycle with this updatedb job. So is it a bug?
-- View this message in context: http://lucene.472066.n3.nabble.com/question-about-running-updatedb-tp4054658p4086585.html Sent from the Nutch - User mailing list archive at Nabble.com.
