[jira] Created: (NUTCH-384) When using the file protocol one can not map a parse plugin to a content type. The only way to get the plugin called is through the default plugin. The issue is that the co

When using the file protocol one can not map a parse plugin to a content type. The only way to get the plugin called is through the default plugin. The issue is that the content type never gets mapped.

[jira] Updated: (NUTCH-384) Protocol-file plugin does not allow the parse plugins framework to operate properly

[ http://issues.apache.org/jira/browse/NUTCH-384?page=all ] Chris A. Mattmann updated NUTCH-384: Summary: Protocol-file plugin does not allow the parse plugins framework to operate properly (was: When using the file protocol one can not map a

[jira] Created: (NUTCH-385) Server delay feature conflicts with maxThreadsPerHost

Server delay feature conflicts with maxThreadsPerHost - Key: NUTCH-385 URL: http://issues.apache.org/jira/browse/NUTCH-385 Project: Nutch Issue Type: Bug Components: fetcher

[jira] Commented: (NUTCH-385) Server delay feature conflicts with maxThreadsPerHost

[ http://issues.apache.org/jira/browse/NUTCH-385?page=comments#action_12441528 ] Chris Schneider commented on NUTCH-385: --- This comment was actually made by Andrzej in response to an email containing the analysis above that I sent him

[jira] Commented: (NUTCH-385) Server delay feature conflicts with maxThreadsPerHost

[ http://issues.apache.org/jira/browse/NUTCH-385?page=comments#action_12441529 ] Chris Schneider commented on NUTCH-385: --- This comment was actually made by Ken Krugler, who was responding to Andrzej's comment above: [with respect to