[
https://issues.apache.org/jira/browse/NUTCH-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410136#comment-16410136
]
Ben Vachon commented on NUTCH-1741:
-----------------------------------
Thank you, [~wastl-nagel] and [~yossi]. That makes much more sense now.
I suppose my situation is unusual. Custom protocol, parser, and signature
plugins in our framework ignore the "http.content.limit" property and stream
buffered content directly to/from a separately managed content store.
Looking at NutchSitemapParser, I realize that's not going to work with the
Nutch sitemaps architecture, so I'd like to also change NutchSitemapParser into
a plugin point (perhaps handled by the ParserFactory) if that makes sense.
> Support of Sitemaps in Nutch 2.x
> --------------------------------
>
> Key: NUTCH-1741
> URL: https://issues.apache.org/jira/browse/NUTCH-1741
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher, generator
> Reporter: Alparslan Avcı
> Assignee: Cihad Guzel
> Priority: Major
> Labels: gsoc2015
> Fix For: 2.4
>
> Attachments: NUTCH-1741-v2.patch, NUTCH-1741-v3.patch,
> NUTCH-1741-v4.patch, NUTCH-1741-webpage-avsc.patch, NUTCH-1741.patch,
> NUTCH-1741v5.patch, NUTCH-1741v6.patch, NUTCH-1741v7.patch,
> SitemapCrawlerLifeCycle.pdf, SitemapDevelopmentFor2x.pdf
>
>
> Sitemap support has to be implemented for 2.x branch. It is being discussed
> in NUTCH-1465 for trunk.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
