[
https://issues.apache.org/jira/browse/NUTCH-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746807#comment-14746807
]
Lewis John McGibbney commented on NUTCH-1679:
---------------------------------------------
I've tested this with Nutch 2.X HEAD, Gora 0.5 and therefore HBase 0.94.14 and
after 4 rounds of crawling updating with batchId all seems to be good. I am not
having pages refetched so it would indicate that the early re-fetch of pages
issue has been eliminated.
I am going to commit this most recent patch then work on driving a 2.3.1
release.
Thanks folks for the patience on this one and thank you all for submitting
various patches.
> UpdateDb using batchId, link may override crawled page.
> -------------------------------------------------------
>
> Key: NUTCH-1679
> URL: https://issues.apache.org/jira/browse/NUTCH-1679
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Tien Nguyen Manh
> Assignee: Lewis John McGibbney
> Priority: Blocker
> Fix For: 2.3.1
>
> Attachments: NUTCH-1679-2.patch, NUTCH-1679.patch, NUTCH-1679_3.patch
>
>
> The problem is in Hbase store, not sure about other store.
> Suppose at first crawl cycle we crawl link A, then get an outlink B.
> In second cycle we crawl link B which also has a link point to A
> In second updatedb we load only page B from store, and will add A as new link
> because it doesn't know A already exist in store and will override A.
> UpdateDb must be run without batchId or we must set additionsAllowed=false
> Here are code for new page
> page = new WebPage();
> schedule.initializeSchedule(url, page);
> page.setStatus(CrawlStatus.STATUS_UNFETCHED);
> try {
> scoringFilters.initialScore(url, page);
> } catch (ScoringFilterException e) {
> page.setScore(0.0f);
> }
> new page will override old page status, score, fetchTime, fetchInterval,
> retries, metadata[CASH_KEY]
> - i think we can change something here so that new page will only update one
> column for example 'link' and if it is really a new page, we can initialize
> all above fields in generator
> - or we add operator checkAndPut to store so when add new page we will check
> if already exist first
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
