You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Doğacan Güney (JIRA)" <ji...@apache.org> on 2007/10/28 20:27:51 UTC
[jira] Updated: (NUTCH-501) Implement a different caching mechanism
for objects cached in configuration
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doğacan Güney updated NUTCH-501:
--------------------------------
Attachment: NUTCH-501_v2.patch
Patch updated for latest trunk.
> Implement a different caching mechanism for objects cached in configuration
> ---------------------------------------------------------------------------
>
> Key: NUTCH-501
> URL: https://issues.apache.org/jira/browse/NUTCH-501
> Project: Nutch
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Doğacan Güney
> Assignee: Doğacan Güney
> Fix For: 1.0.0
>
> Attachments: NUTCH-501.patch, NUTCH-501_draft.patch, NUTCH-501_draft_v2.patch, NUTCH-501_v2.patch
>
>
> As per HADOOP-1343, Configuration.setObject and Configuration.getObject (which are used by Nutch to cache arbitrary objects) are deprecated and will be removed soon. We have to implement an alternative caching mechanism and replace all usages of Configuration.{getObject,setObject} with the new mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.