Actually, patch provided in the original issue https://issues.apache.org/jira/browse/NUTCH-1714 is not completely applicable to the current trunk, because nutch code has been changed since. I modified original patch in order to apply to the current trunk. I can combine modifed patch with the changes I made to the code and generate new patch. If this is not advisable, please let me know.
Thanks. Alex. -----Original Message----- From: Lewis John Mcgibbney <[email protected]> To: user <[email protected]> Sent: Fri, Apr 11, 2014 1:46 pm Subject: Re: nutch-2.x with hbase filter option Hi Alex, Regarding your findings and the code you've posted. Can you please open an issue on Jira, posting in the code changes (or even better a patch :) ) If you could like it to the Gora 0.4 upgrade issue in Nutch Jira it would be excellent. Thanks v much Alex. Lewis On Fri, Apr 11, 2014 at 11:14 AM, <[email protected]> wrote: > > It turned out that the error is generated because of the mismatch of the > new function's return type(Integer) and the resulting variable. After > changing these lines > in > > SNIP > TO > Integer interval = page.getFetchInterval(); > switch (state) { > case FetchSchedule.STATUS_MODIFIED: > interval *=(int) (1.0f - DEC_RATE); > break; > case FetchSchedule.STATUS_NOTMODIFIED: > interval *=(int) (1.0f + INC_RATE); > break; > case FetchSchedule.STATUS_UNKNOWN: > break; > } > >
