An alternative to removing it from the codebase is to override all use of
MapWritable by explicitly using o.g.apache.hadoop.io.MapWritable
e.g.
if (version > 3) {
boolean hasMetadata = false;
if (version < 7) {
org.apache.hadoop.io.MapWritable oldMetaData = new
org.apache.hadoop.io.MapWritable();
which works :0)
On Sun, Feb 26, 2012 at 2:58 PM, Lewis John Mcgibbney <
[email protected]> wrote:
> Hi Guys,
>
> This class has been deprecated since bore Nutch 1.1, is there any reason
> we still ship with it?
> The reason I ask is that when attending to NUTCH-1273, I thought rather
> than patching over the issues with @SupressWarnings("deprecated"), it would
> be more fitting to address the issue of our use of deprecated classes head
> on... by using the new dependency API's.
>
> The problem with this particular class is that the Nutch MapWritable seems
> to take precedence over the imported Hadoop one, I am guessing this is
> because of course Nutch classes are local and in this case MapWritable is
> in the same package as CrawlDatum so it is used.
>
> Does anyone have a problem with this? Or can anyone see any adverse
> repercussions as a result of removing this class?
>
> Thanks
>
> Lewis
>
> --
> *Lewis*
>
>
--
*Lewis*
