[ http://issues.apache.org/jira/browse/NUTCH-34?page=all ]
Chris A. Mattmann resolved NUTCH-34:
------------------------------------
Fix Version: 0.7.2-dev
0.8-dev
Resolution: Fixed
This issue was addressed via the application of NUTCH-88 applied to Nutch
0.7.2-dev and Nutch 0.8-dev. The only thing not addressed by this issue was the
addition of a content-length attribute to a particular parsing plugin declaring
a parse plugins ability to handle some content length amount. I recommend if
that becomes an important issue to address, that a separate JIRA issue be
created for that particular functionality.
> Parsing different content formats
> ---------------------------------
>
> Key: NUTCH-34
> URL: http://issues.apache.org/jira/browse/NUTCH-34
> Project: Nutch
> Type: Improvement
> Components: fetcher
> Reporter: Stephan Strittmatter
> Priority: Trivial
> Fix For: 0.7.2-dev, 0.8-dev
>
> At the moment Nuch is set up to filter content by config the xml-config file.
> There it is also set global how many bytes are loaded.
> I think it yould be better to let the parser plugins "register" themselfe in
> some registry where every plugin could tell the fetcher, that:
> 1. this document type is wanted (because the parser plugin is
> installed and activated)
> 2. how much of the content is required (some plugins need the whole
> content and some not)
--
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
