giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-13) Port Giraph to YARN
Date Fri, 29 Mar 2013 02:19:15 GMT

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

Hyunsik Choi commented on GIRAPH-13:
------------------------------------

Eli,

+1
Great job! Since you started this work, you have improved many things and fixed from comments
for long time. In my opinion, now there are no things to be improved. I think that this work
is the most written yarn client code that I have seen so far.
                
> Port Giraph to YARN
> -------------------
>
>                 Key: GIRAPH-13
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-13
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Jakob Homan
>            Assignee: Eli Reisman
>         Attachments: GIRAPH-13-1.patch, GIRAPH-13-2.patch, GIRAPH-13-3.patch, GIRAPH-13-4.patch,
GIRAPH-13-5.patch, GIRAPH-13-6.patch, GIRAPH-13-7.patch, GIRAPH-13-8.patch, GIRAPH-13-9.patch,
GIRAPH-13-9-r1.patch, GIRAPH-13-9-r2.patch, GIRAPH-13-9-r3.patch, GIRAPH-13-9-r4.patch, GIRAPH-13-9-r5.patch,
GIRAPH-13-9-r6.patch
>
>
> Now that YARN (aka MR2 aka MAPREDUCE-279) has been merged into the Hadoop trunk, we should
think about what it would take to separate out the graph processing bits of Giraph from the
MR1-specific code so as to take advantage of the less-MR centric aspects of YARN, while still
supporting both over the medium term.
> Review Board link (ready for review now): https://reviews.apache.org/r/9811/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message