Implement a different caching mechanism for objects
cached in configuration
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
[ https://issues.apache.org/jira/browse/NUTCH-501?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505793 ]=20
Enis Soztutar commented on NUTCH-501:
-------------------------------------
I think we should make ObjectCache a singleton in case we need to put other=
fields later.=20
> 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
>
> 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 mec=
hanism.
--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
