[ 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 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.)
Description: 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. Currently the
content type does not get set by the file protocol. (was: Currently the
content type does not get set by the file protocol.)
Moved title into description and made shorter title.
> Protocol-file plugin does not allow the parse plugins framework to operate
> properly
> -----------------------------------------------------------------------------------
>
> Key: NUTCH-384
> URL: http://issues.apache.org/jira/browse/NUTCH-384
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 0.8.1, 0.8
> Environment: All
> Reporter: Paul Ramirez
>
> 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. Currently the content
> type does not get set by the file protocol.
--
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
