[ http://issues.apache.org/jira/browse/NUTCH-273?page=all ]
Eelco Lempsink updated NUTCH-273: --------------------------------- Attachment: Fetcher.java-489586.diff Let's not overcomplicate this issue. At the moment, two different problems of different priorities are mixed in one issue. Problem 1, blocker: The status of the URL causing the redirect isn't updated. Fixing that is not hard, attached is a one-liner patch. Hopefully this can be applied soon. Problem 2, minor: Should redirects be fetched immediately or not? One argument to fetch it immediately is that otherwise the redirectCount should be moved into the CrawlDatum (metadata). If it's possible (in Jira) I suggest this problem should be split into a different issue. > When a page is redirected, the original url is NOT updated. > ----------------------------------------------------------- > > Key: NUTCH-273 > URL: http://issues.apache.org/jira/browse/NUTCH-273 > Project: Nutch > Issue Type: Bug > Components: fetcher > Affects Versions: 0.8 > Environment: n/a > Reporter: Lukas Vlcek > Priority: Blocker > Attachments: Fetcher.java-489586.diff > > > [Excerpt from maillist, sender: Andrzej Bialecki] > When a page is redirected, the original url is NOT updated - so, CrawlDB will > never know that a redirect occured, it won't even know that a fetch > occured... This looks like a bug. > In 0.7 this was recorded in the segment, and then it would affect the Page > status during updatedb. It should do so 0.8, too... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira