[
https://issues.apache.org/jira/browse/NUTCH-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473184
]
Doğacan Güney commented on NUTCH-443:
-------------------------------------
Andrzej:
Why does fetcher need to synchronize? Why does the order fetcher outputs <key,
value> pairs matters?
Sami:
> I opened an issue for this NUTCH-434 and I am now recommending that the patch
> in this issue
> doesn't try to take the world in one piece :)
Right. I just realized just how much this patch changes and most of them are
not necessary for the proposed API change. So I am going to post a version that
uses ObjectWritable in Fetcher, doesn't remove FetcherOutputFormat and only
changes parse-rss so that it works with the new API (sorry about that Renaud,
but parse-rss can be updated after this patch)
> allow parsers to return multiple Parse object, this will speed up the rss
> parser
> --------------------------------------------------------------------------------
>
> Key: NUTCH-443
> URL: https://issues.apache.org/jira/browse/NUTCH-443
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher
> Affects Versions: 0.9.0
> Reporter: Renaud Richardet
> Assigned To: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: NUTCH-443-draft-v1.patch, NUTCH-443-draft-v2.patch,
> NUTCH-443-draft-v3.patch, NUTCH-443-draft-v4.patch, NUTCH-443-draft-v5.patch,
> NUTCH-443-draft-v6.patch, parse-map-core-draft-v1.patch,
> parse-map-core-untested.patch, parsers.diff
>
>
> allow Parser#parse to return a Map<String,Parse>. This way, the RSS parser
> can return multiple parse objects, that will all be indexed separately.
> Advantage: no need to fetch all feed-items separately.
> see the discussion at
> http://www.nabble.com/RSS-fecter-and-index-individul-how-can-i-realize-this-function-tf3146271.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
