nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doğacan Güney (JIRA) <j...@apache.org>
Subject [jira] Updated: (NUTCH-501) Implement a different caching mechanism for objects cached in configuration
Date Mon, 18 Jun 2007 13:35:25 GMT

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

Doğacan Güney updated NUTCH-501:
--------------------------------

    Summary: Implement a different caching mechanism for objects cached in configuration 
(was: implementing a different caching mechanism for objects
Implement a different caching mechanism for objects cached in configuration)

Trying to fix the messed up title.

> 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
>             Fix For: 1.0.0
>
>         Attachments: NUTCH-501_draft.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.


Mime
View raw message