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/06/18 14:04:26 UTC
[jira] Created: (NUTCH-501) implementing a different caching
mechanism for objects
Implement a different caching mechanism for objects
cached in configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
implementing a different caching mechanism for objects
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=C4=9Facan G=C3=BCney
Fix For: 1.0.0
As per HADOOP-1343, Configuration.setObject and Configuration.getObject (wh=
ich are used by Nutch to cache arbitrary objects) are deprecated and will b=
e removed soon. We have to implement an alternative caching mechanism and r=
eplace all usages of Configuration.{getObject,setObject} with the new mecha=
nism.
--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Enzo Michelangeli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507678 ]
Enzo Michelangeli commented on NUTCH-501:
-----------------------------------------
Doğacan Güney - [23/Jun/07 12:11 PM ]:
> Actually, you are right. It is a bug. However, that bug is irrelevant in *this* case.
> Notice that PluginRepository runs out of memory not because we have too
> many active configurations at once. We run out of memory, because, for some
> reason that I don't quite understand yet, loaded plugin classes don't get 'unloaded'.
It seems to me that implementing plugin loading through class loading presents some drawbacks. http://java.sun.com/docs/books/jls/unloading-rationale.html explains that class unloading is just an optimization, and "the semantics of a program should not depend on whether and how a system chooses to implement an optimization such as class unloading. To do otherwise would completely compromise the portability of Java programs. Consequently, whether a class has been unloaded or not should be transparent to a Java program". However, I'd like to have some control over plugin loading/unloading. It's not only matter of memory leaks: sometimes unloading, especially when unexpected, is just unwelcome. In particular, I'd like have a method (finalize() ?) guaranteed to be called when the plugin is unloaded in order to perform some cleanup (e.g., close open files and/or database connections), and also have an option to make the plugin "sticky", with the guarantee that it will not be unloaded (in case the plugin initialization happened to be particularly expensive). But, in the present implementation, that would require my code to have visibility over class loading/unloading, which is frowned upon...
> 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.patch, NUTCH-501_draft.patch, NUTCH-501_draft_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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Nicolás Lichtmaier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507618 ]
Nicolás Lichtmaier commented on NUTCH-501:
------------------------------------------
Doesn't this patch has the same bug the plugin respository has now? Won't different configuration, which are the same, get different caches?
> 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, NUTCH-501_draft_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.
[jira] Updated: (NUTCH-501) Implement a different caching mechanism
for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ 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.patch
New version. Added a debug statement to ObjectCache instantiation as Andrzej suggested.
> 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.patch, NUTCH-501_draft.patch, NUTCH-501_draft_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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "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_12507626 ]
Doğacan Güney commented on NUTCH-501:
-------------------------------------
> Doesn't this patch has the same bug the plugin respository has now? Won't different configuration, which are the same, get different caches?
It is not a bug, it is a feature :). See Andrzej's earlier comment for why we need different caches from different configurations that happen to contain the same key/value pairs.
Actually, you are right. It is a bug. However, that bug is irrelevant in *this* case. Notice that PluginRepository runs out of memory not because we have too many active configurations at once. We run out of memory, because, for some reason that I don't quite understand yet, loaded plugin classes don't get 'unloaded'. So, if you are running locally and you have say n total map/reduce tasks, for each new task, nutch reloads all plugin classes again and doesn't unload them when task is done. So, ObjectCache only leaks stuff that PluginRepository leaks anyway (at worst, the overhead is just an extra reference to the leaked object). Everything else will be garbage collected when a configuration is no longer in use.
To sum up: Yes, different configurations will get different caches. But I believe that this will not cause (any more) problems. Feel free to prove me wrong :).
> 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, NUTCH-501_draft_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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "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_12505815 ]
Doğacan Güney commented on NUTCH-501:
-------------------------------------
Thanks for the quick review, Andrzej.
I guess we can solve that problem by going down the PluginRepository way. We add a static WeakHashMap<Configuration, ObjectCache> to ObjectCache, make CACHE an instance member and add a static ObjectCache.get(Configuration) method. So one would use ObjectCache like:
ObjectCache.get(conf).getObject(...)
If that particular configuration instance does not have an associated ObjectCache, get will first create a new ObjectCache then put it in WeakHashMap. When that configuration is no longer used, GC will collect it.
As you know, this doesn't work for PluginRepository. New configurations instantiate new PluginRepository-s while, for some reason that I don't understand (I should really study how dynamic class loading works), old PluginRepository-s don't get collected. But this should not be a problem for ObjectCache, since whatever is not collected in ObjectCache will also be in a PluginRepository(thus, it wouldn't have been collected anyway) and everything else will be collected.
What do you think?
> 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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Andrzej Bialecki (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507609 ]
Andrzej Bialecki commented on NUTCH-501:
-----------------------------------------
+1 - looks good. An idea: perhaps we could add a LOG.debug() statement in ObjectCache.get() to trace the creation of ObjectCache instances, at least initially, to see how many instances are created per a single map-reduce task (should be just 1).
> 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, NUTCH-501_draft_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.
[jira] Assigned: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doğacan Güney reassigned NUTCH-501:
-----------------------------------
Assignee: Doğacan Güney
> 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.
[jira] Updated: (NUTCH-501) Implement a different caching mechanism
for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ 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_draft_v2.patch
Second draft of the patch. This is pretty much the realization of my previous comment.
> 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, NUTCH-501_draft_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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "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_12537938 ]
Doğacan Güney commented on NUTCH-501:
-------------------------------------
Dennis, are you working on updating it? If not, I can update it over the weekend...
> 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.patch, NUTCH-501_draft.patch, NUTCH-501_draft_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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Andrzej Bialecki (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538512 ]
Andrzej Bialecki commented on NUTCH-501:
-----------------------------------------
+1
> 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.
[jira] Updated: (NUTCH-501) Implement a different caching mechanism
for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538655 ]
Hudson commented on NUTCH-501:
------------------------------
Integrated in Nutch-Nightly #251 (See [http://lucene.zones.apache.org:8080/hudson/job/Nutch-Nightly/251/])
> 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.
[jira] Commented: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Dennis Kubes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537736 ]
Dennis Kubes commented on NUTCH-501:
------------------------------------
The current patch no longer compiles with current codebase.
> 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.patch, NUTCH-501_draft.patch, NUTCH-501_draft_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.
[jira] Issue Comment Edited: (NUTCH-501) Implement a different
caching mechanism for objects cached in configuration
Posted by "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.
[jira] Resolved: (NUTCH-501) Implement a different caching
mechanism for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doğacan Güney resolved NUTCH-501.
---------------------------------
Resolution: Fixed
Committed in rev. 589654. I am working in a new environment now, so I hope I got everything right.
> 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.
[jira] Updated: (NUTCH-501) Implement a different caching mechanism
for objects cached in configuration
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ 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.