[ http://issues.apache.org/jira/browse/NUTCH-244?page=comments#action_12373393 ]
Jerome Charron commented on NUTCH-244: -------------------------------------- While taking a quick look at this, something astonished me in the code. The db.max.outlinks.per.page property is exclusively used in ParseData. In the ParseData, the number of outlinks used is filtered in the readFields method ... Shouldn't it be directly filtered in the ParseData constructor ? > Inconsistent handling of property values boundaries / unable to set > db.max.outlinks.per.page to infinite > -------------------------------------------------------------------------------------------------------- > > Key: NUTCH-244 > URL: http://issues.apache.org/jira/browse/NUTCH-244 > Project: Nutch > Type: Bug > Versions: 0.8-dev > Reporter: AJ Banck > > Some properties like file.content.limit support using negative numbers (-1) > to 'disable' a limitation. > Other properties do not support this. > I tried disabling the limit set by db.max.outlinks.per.page, but this isn't > possible. -- 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
