nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Nagel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-2049) Upgrade Trunk to Hadoop > 2.6 stable
Date Wed, 01 Jul 2015 12:53:04 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610062#comment-14610062
] 

Sebastian Nagel commented on NUTCH-2049:
----------------------------------------

Linked to
* NUTCH-1936 (part of): of course, a GSoC project could include moving to the new MapReduce
API and could apply to Nutch 2.x as well
* NUTCH-1712 (blocks): we cannot move injector to the new MapReduce API because of a missing
output format class in Hadoop 1.2.0. It's available in 2.6: [o.a.h.mapreduce.lib.output.MapFileOutputFormat|http://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/mapreduce/lib/output/MapFileOutputFormat.html]

> Upgrade Trunk to Hadoop > 2.6 stable
> ------------------------------------
>
>                 Key: NUTCH-2049
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2049
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build
>            Reporter: Lewis John McGibbney
>             Fix For: 1.11
>
>
> Convo here - http://www.mail-archive.com/dev%40nutch.apache.org/msg18225.html
> I am +1 for taking trunk (or a branch of trunk) to explicit dependency on > Hadoop
2.6.
> We can run our tests, we can validate, we can fix.
> I will be doing validation on 2.X in paralegal as this is what I use on my own projects.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message