[jira] Issue Comment Edited: (NUTCH-501) Implement a different caching mechanism for objects cached in configuration

["Doğacan Güney (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538333 ] 

dogacan edited comment on NUTCH-501 at 10/28/07 12:28 PM:
----------------------------------------------------------------

Patch updated for latest trunk.

I ran a small crawl with it with no problems. So I am going to commit it if there are no objections.

      was (Author: dogacan):
    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.