[jira] Updated: (NUTCH-501) implementing a different caching mechanism for objects

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

Implement a different caching mechanism for objects
 cached in configuration
In-Reply-To: <25...@brutus>
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:all-tabpanel ]

Do=C4=9Facan G=C3=BCney updated NUTCH-501:
--------------------------------

    Attachment: NUTCH-501_draft.patch

First draft of the patch.

* Adds a new ObjectCache class that is just a map from Strings to Objects.

* Replaces all usages of Configuration.setObject and Configuration.getObjec=
t with ObjectCache's methods.

Most unit tests pass. One of the tests from TestGenerator fails for some re=
ason (I am looking into it).=20

I also successfully ran a basic crawl with this patch.=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.