[ 
https://issues.apache.org/jira/browse/NUTCH-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451246#comment-17451246
 ] 

ASF GitHub Bot commented on NUTCH-2911:
---------------------------------------

sebastian-nagel commented on pull request #708:
URL: https://github.com/apache/nutch/pull/708#issuecomment-982823043


   Thanks @prakharchaube, good catch. The compilation fails with 
`Fetcher.java:440: error: unreported exception InterruptedException; must be 
caught or declared to be thrown` - could you update the PR to catch the 
exception thrown by the 
[cleanup](https://hadoop.apache.org/docs/r3.3.1/api/org/apache/hadoop/mapreduce/Mapper.html#cleanup-org.apache.hadoop.mapreduce.Mapper.Context-)
 method. Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


> Add cleanup call in Fetcher.java
> --------------------------------
>
>                 Key: NUTCH-2911
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2911
>             Project: Nutch
>          Issue Type: Improvement
>          Components: fetcher
>            Reporter: Prakhar Chaube
>            Priority: Minor
>              Labels: improvement
>
> Fetcher's inner class, FetcherRun overrides Hadoop Mapper's run().
> Even though Nutch's FetcherRun doesn't need an explicit call the Mapper's 
> cleanup() (Which is a blank function), it would increase the readability and 
> completeness of the run Method to do so.
> Ideally, every implementation of Mapper is supposed to do the following tasks:
> 1. Perform Setup
> 2.  Call map on the data set
> 3. Perform cleanups.
> Moreover, in case a custom Fetcher is written extending Fetcher.java cleanup 
> could get easily missed out.
> PR for Fix: [here|https://github.com/apache/nutch/pull/708]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to