You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2007/03/10 07:54:09 UTC
[jira] Closed: (NUTCH-384) Protocol-file plugin does not allow the
parse plugins framework to operate properly
[ https://issues.apache.org/jira/browse/NUTCH-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann closed NUTCH-384.
-----------------------------------
Patch applied, with whitespace changes, and unit test (contributed by yours truly):
http://svn.apache.org/viewvc?view=rev&revision=516660
Thanks, Heiko!
> Protocol-file plugin does not allow the parse plugins framework to operate properly
> -----------------------------------------------------------------------------------
>
> Key: NUTCH-384
> URL: https://issues.apache.org/jira/browse/NUTCH-384
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 0.8, 0.8.1, 0.9.0
> Environment: All
> Reporter: Paul Ramirez
> Assigned To: Chris A. Mattmann
> Fix For: 0.9.0
>
> Attachments: file_protocol_mime_patch.diff
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.