You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Eli Reisman (JIRA)" <ji...@apache.org> on 2013/12/08 19:44:35 UTC

[jira] [Commented] (GIRAPH-794) add support for generic hadoop1 and hadoop2 profiles

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

Eli Reisman commented on GIRAPH-794:
------------------------------------

i like this idea, does anyone have a problem with this?

> add support for generic hadoop1 and hadoop2 profiles
> ----------------------------------------------------
>
>                 Key: GIRAPH-794
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-794
>             Project: Giraph
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.0.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 1.1.0
>
>         Attachments: 0001-GIRAPH-794.-add-support-for-generic-hadoop1-and-hado.patch
>
>
> I would like to propose that as part of Giraph 1.1.0 we introduce generic hadoop1 and hadoop2 profiles that would be expected to track latest releases on hadoop 1.x and hadoop 2.x codelines (currently these are 1.2.1 and 2.2.0). These profiles will be the ones used to publish Giraph maven artifacts. Following the convention established by HBase I propose that we bake hadoop1 and hadoop2 tokens into a version.
> Thus every release of Giraph starting from 1.1.0 will deploy the following versions:
>    * <version> (same as <version>-hadoop1)
>    * <version>-hadoop1
>    * <version>-hadoop2
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.1#6144)