[jira] [Updated] (GIRAPH-51) Provide unit testing tool for Giraph algorithms
[
https://issues.apache.org/jira/browse/GIRAPH-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Schelter updated GIRAPH-51:
-
Attachment: GIRAPH-51.patch
Hi, I'm currently trying to find a way to easily unit test giraph algorithms as
suggested here. I plan to implement some complicated stuff on top of Giraph and
definitely need this functionality for debugging and development.
I want to be able to repeatedly run a Vertex class in a unit test from my IDE
without having to cleanup directories or rely on an external zookeeper instance.
I managed to get a working prototype of a class that can internally run a
Vertex. I had to add configuration options to disable the starting of a
zookeeper instance via ProcessBuilder in ZooKeeperManager as this didn't work
out of my IDE (Intellij). My testing class simply starts its own zookeeper in
an extra thread for the duration of the test. This works pretty well and I was
already able to unit the SimpleShortestPathVertex.
Although everything seems to work, I'm still getting some strange warnings from
the local zookeeper instance. As I'm not that familiar with zookeeper yet, I
wanted ask here whether these warning can simply be ignored?
{quote}
11/11/11 09:55:16 INFO server.PrepRequestProcessor: Got user-level
KeeperException when processing sessionid:0x13391d6887b0001 type:create
cxid:0x1 zxid:0xfffe txntype:unknown reqpath:n/a Error
Path:/_hadoopBsp/job_local_0001 Error:KeeperErrorCode = NoNode for
/_hadoopBsp/job_local_0001
{quote}
{quote}
WARN graph.BspService: process: Unknown and unprocessed event
(path=/_hadoopBsp/job_local_0001/_applicationAttemptsDir/0/_superstepDir,
type=NodeChildrenChanged, state=SyncConnected)
{quote}
Already putting up a first patch for clarity.
Best,
Sebastian
Provide unit testing tool for Giraph algorithms
---
Key: GIRAPH-51
URL: https://issues.apache.org/jira/browse/GIRAPH-51
Project: Giraph
Issue Type: Improvement
Reporter: Jakob Homan
Attachments: GIRAPH-51.patch
It would be nice to have a little tool, similar to MRUnit, that would allow
Giraph application writers to quickly unit test their algorithms. The tool
could take a Vertex implementation, a set of input and expected output and
verify that after the specified number of supersteps, we've gotten what we
expect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GIRAPH-63) Typo in PageRankBenchmark
[
https://issues.apache.org/jira/browse/GIRAPH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148579#comment-13148579
]
Shaunak Kashyap commented on GIRAPH-63:
---
Also found the same typo in
{{org/apache/giraph/benchmark/RandomMessageBenchmark.java}}:
{code:title=RandomMessageBenchmark.java|borderStyle=solid}
if (!cmd.hasOption('s')) {
System.out.println(Need to set the number of supesteps (-s));
return -1;
}
{code}
Typo in PageRankBenchmark
-
Key: GIRAPH-63
URL: https://issues.apache.org/jira/browse/GIRAPH-63
Project: Giraph
Issue Type: Bug
Reporter: Jakob Homan
Priority: Trivial
Labels: newbie
{code:title=PageRankBenchmark.java|borderStyle=solid}
if (!cmd.hasOption('s')) {
System.out.println(Need to set the number of supesteps (-s));
return -1;
}{code}
supesteps - supersteps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Newbie wanting to get involved with Giraph development
Thanks for the advice Claudio and Avery. I've read the trunk/CODE_CONVENTIONS file and will submit my patch for review on https://reviews.apache.org. One more question: Even though I have signed up for a JIRA account I am unable to assign GIRAPH-63 to myself. Do I need to be added to the GIRAPH project by someone before I can do that? Or do I just start work without assigning this to myself? Thanks, Shaunak On Thu, Nov 10, 2011 at 10:14 AM, Avery Ching ach...@apache.org wrote: Claudio gave great advice. The only thing I'd like to add is that you also might want to consider using reviewboard for throwing up patches (https://reviews.apache.org/) as it helps to get line-by-line comments and suggestions. Definitely email the mailing lists if you have questions and have fun! Avery On 11/10/11 9:40 AM, Claudio Martella wrote: Hi, I don't know if there's anything such as an official Development Process, I can share how I usually do when I contribute to ASF projects. (1) Considering there's already an open issue (a ticket in the JIRA) I'd download from SVN the version to which the issue applies, I'd write the fix, test it through unittests that come with the project (and fix them if necessary) and create the patch (svn diff ISSUE.diff is the way I do) that I later attach it to the issue. (2) If there's not open issue yet about a bug or a feature missing, if it's trivial (such as the one you've chosen) I'd write the patch as in (1) and open the issue describing the problem by attaching the fix. If it's not trivial I'd open the issue and wait for some contribution to the discussion. Learn from the other issues you find on the JIRA. Make sure to follow CODE_CONVENTIONS file ( ;-) ). I'm expecting the experts to give more insights about the process. Hope this helps, Claudio On Thu, Nov 10, 2011 at 5:56 PM, Shaunak Kashyapycombina...@gmail.com wrote: Hi, I'm a newbie to Giraph and ASF projects in general. I would like to help with Giraph development and think I've found the perfect JIRA to start: https://issues.apache.org/jira/browse/GIRAPH-63. Before I make any code changes, however, I'd like to know more about the development process of this project. What is a good place to start learning about this? Thank you, Shaunak -- Now the hardness of this world slowly grinds your dreams away / Makin' a fool's joke out of the promises we make --- Bruce Springsteen, Blood Brothers -- Now the hardness of this world slowly grinds your dreams away / Makin' a fool's joke out of the promises we make --- Bruce Springsteen, Blood Brothers
Re: Newbie wanting to get involved with Giraph development
I'll add you as a contributor and assign 63 to you. Go ahead and get started. Thanks for the contribution! On Fri, Nov 11, 2011 at 9:15 AM, Shaunak Kashyap ycombina...@gmail.com wrote: Thanks for the advice Claudio and Avery. I've read the trunk/CODE_CONVENTIONS file and will submit my patch for review on https://reviews.apache.org. One more question: Even though I have signed up for a JIRA account I am unable to assign GIRAPH-63 to myself. Do I need to be added to the GIRAPH project by someone before I can do that? Or do I just start work without assigning this to myself? Thanks, Shaunak On Thu, Nov 10, 2011 at 10:14 AM, Avery Ching ach...@apache.org wrote: Claudio gave great advice. The only thing I'd like to add is that you also might want to consider using reviewboard for throwing up patches (https://reviews.apache.org/) as it helps to get line-by-line comments and suggestions. Definitely email the mailing lists if you have questions and have fun! Avery On 11/10/11 9:40 AM, Claudio Martella wrote: Hi, I don't know if there's anything such as an official Development Process, I can share how I usually do when I contribute to ASF projects. (1) Considering there's already an open issue (a ticket in the JIRA) I'd download from SVN the version to which the issue applies, I'd write the fix, test it through unittests that come with the project (and fix them if necessary) and create the patch (svn diff ISSUE.diff is the way I do) that I later attach it to the issue. (2) If there's not open issue yet about a bug or a feature missing, if it's trivial (such as the one you've chosen) I'd write the patch as in (1) and open the issue describing the problem by attaching the fix. If it's not trivial I'd open the issue and wait for some contribution to the discussion. Learn from the other issues you find on the JIRA. Make sure to follow CODE_CONVENTIONS file ( ;-) ). I'm expecting the experts to give more insights about the process. Hope this helps, Claudio On Thu, Nov 10, 2011 at 5:56 PM, Shaunak Kashyapycombina...@gmail.com wrote: Hi, I'm a newbie to Giraph and ASF projects in general. I would like to help with Giraph development and think I've found the perfect JIRA to start: https://issues.apache.org/jira/browse/GIRAPH-63. Before I make any code changes, however, I'd like to know more about the development process of this project. What is a good place to start learning about this? Thank you, Shaunak -- Now the hardness of this world slowly grinds your dreams away / Makin' a fool's joke out of the promises we make --- Bruce Springsteen, Blood Brothers -- Now the hardness of this world slowly grinds your dreams away / Makin' a fool's joke out of the promises we make --- Bruce Springsteen, Blood Brothers
[jira] [Assigned] (GIRAPH-63) Typo in PageRankBenchmark
[
https://issues.apache.org/jira/browse/GIRAPH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan reassigned GIRAPH-63:
-
Assignee: Shaunak Kashyap
Typo in PageRankBenchmark
-
Key: GIRAPH-63
URL: https://issues.apache.org/jira/browse/GIRAPH-63
Project: Giraph
Issue Type: Bug
Reporter: Jakob Homan
Assignee: Shaunak Kashyap
Priority: Trivial
Labels: newbie
{code:title=PageRankBenchmark.java|borderStyle=solid}
if (!cmd.hasOption('s')) {
System.out.println(Need to set the number of supesteps (-s));
return -1;
}{code}
supesteps - supersteps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Review Request: GIRAPH-63: Typo in PageRankBenchmark
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2807/ --- Review request for giraph. Summary --- Fixing typo supestep - superstep. This addresses bug GIRAPH-63. https://issues.apache.org/jira/browse/GIRAPH-63 Diffs - http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/benchmark/PageRankBenchmark.java 1200720 http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/benchmark/RandomMessageBenchmark.java 1200720 Diff: https://reviews.apache.org/r/2807/diff Testing --- $ mvn test Thanks, shaunak
[jira] [Commented] (GIRAPH-63) Typo in PageRankBenchmark
[
https://issues.apache.org/jira/browse/GIRAPH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148592#comment-13148592
]
Jakob Homan commented on GIRAPH-63:
---
Ah, thanks. Actually, for some reason, JIRA hides this option with its latest
upgrade. On More Actions there's an Attach File option that will upload the
patch file itself. Then we can download this and apply it to the tree. Looks
good though, from what was pasted in!
Typo in PageRankBenchmark
-
Key: GIRAPH-63
URL: https://issues.apache.org/jira/browse/GIRAPH-63
Project: Giraph
Issue Type: Bug
Reporter: Jakob Homan
Assignee: Shaunak Kashyap
Priority: Trivial
Labels: newbie
Attachments: GIRAPH-63.diff
{code:title=PageRankBenchmark.java|borderStyle=solid}
if (!cmd.hasOption('s')) {
System.out.println(Need to set the number of supesteps (-s));
return -1;
}{code}
supesteps - supersteps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GIRAPH-63) Typo in PageRankBenchmark
[
https://issues.apache.org/jira/browse/GIRAPH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148598#comment-13148598
]
Jakob Homan commented on GIRAPH-63:
---
Perfect, thanks! +1 on the patch. Will commit shortly.
Typo in PageRankBenchmark
-
Key: GIRAPH-63
URL: https://issues.apache.org/jira/browse/GIRAPH-63
Project: Giraph
Issue Type: Bug
Reporter: Jakob Homan
Assignee: Shaunak Kashyap
Priority: Trivial
Labels: newbie
Attachments: GIRAPH-63.diff
{code:title=PageRankBenchmark.java|borderStyle=solid}
if (!cmd.hasOption('s')) {
System.out.println(Need to set the number of supesteps (-s));
return -1;
}{code}
supesteps - supersteps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GIRAPH-75) Create sections on how to get involved and how to generate patches on website
[ https://issues.apache.org/jira/browse/GIRAPH-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated GIRAPH-75: -- Attachment: GIRAPH-75.patch Patch that adds these sections. It's a big enough change to get another set of eyes on. Since I wrote it, it's heavily weighted toward my style of developing, but I don't think it's too far outside the mainstream. I didn't even say anything mean about rb. Create sections on how to get involved and how to generate patches on website - Key: GIRAPH-75 URL: https://issues.apache.org/jira/browse/GIRAPH-75 Project: Giraph Issue Type: Improvement Reporter: Jakob Homan Assignee: Jakob Homan Attachments: GIRAPH-75.patch We've had several questions lately on how to get started. It would be good to document this on the site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Removed Giraph from November 2011 report
Hey Guys, Giraph reported in August 2011, September 2011 and in October 2011, so I think it's out of the monthly reporting cycle. I removed it from the: http://wiki.apache.org/incubator/November2011 page. Please correct me if I'm wrong. Thanks! Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: better way to update site?
+1. Having the pre-generated files in svn is good enough for me. Avery On 11/11/11 1:36 PM, Jakob Homan wrote: As Avery documented in GIRAPH-36 (https://issues.apache.org/jira/browse/GIRAPH-35?focusedCommentId=13107195page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13107195) it's pretty painful to update the site currently. This is due to the fact that we're keeping the site within the src tree (as dictated by mvn), so we can't just check it out, as other, ant/forrest projects do. The other project I found that does this is hbase, which avoids the whole mess by not keeping their site (ie the contents of people.apache.org/www/incubator/giraph) in svn, but rather generating the site locally and then copying straight to that directory. I think this may be a better approach since it avoids the huge churn of rming and re-creating the whole site structure each time. In this schema, once the site is updated, run mvn site:site to generate its contents, verify its correctness, then scp it to people.apache.org and replace the current directory. (or rsync it and be done). We'll still have all the history of the site, etc., just none of the hassle. What do people think?
[jira] [Commented] (GIRAPH-64) Create VertexRunner to make it easier to run users' computations
[
https://issues.apache.org/jira/browse/GIRAPH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148936#comment-13148936
]
jirapos...@reviews.apache.org commented on GIRAPH-64:
-
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2700/
---
(Updated 2011-11-12 02:03:20.188294)
Review request for giraph.
Summary
---
create giraphrunner
This addresses bug GIRAPH-64.
https://issues.apache.org/jira/browse/GIRAPH-64
Diffs
-
/trunk/bin/giraph PRE-CREATION
/trunk/pom.xml 1196926
/trunk/src/main/assembly/assembly.xml PRE-CREATION
/trunk/src/main/java/org/apache/giraph/GiraphRunner.java PRE-CREATION
/trunk/src/main/java/org/apache/giraph/graph/GraphMapper.java 1196926
Diff: https://reviews.apache.org/r/2700/diff
Testing
---
Thanks,
Jakob
Create VertexRunner to make it easier to run users' computations
Key: GIRAPH-64
URL: https://issues.apache.org/jira/browse/GIRAPH-64
Project: Giraph
Issue Type: New Feature
Reporter: Jakob Homan
Assignee: Jakob Homan
Attachments: GIRAPH-64.patch
Currently, if a user wants to implement a Giraph algorithm by extending
{{Vertex}} they must also write all the boilerplate around the {{Tool}}
interface and bundle it with the Giraph jar (or get Giraph on the classpath
and playing nice with the implementation). For example, what is included in
the PageRankBenchmark and what Kohei has done:
https://github.com/smly/java-Giraph-LabelPropagation It would be better if
we had perhaps a Vertex implementation to be subclassed that already had all
the standard Tooling included such that all one had to run would be (assuming
the Giraph jar was already on the classpath):
{noformat}hadoop jar my-awesome-vertex.jar my.awesome.vertex -i jazz_input -o
jazz_output -if org.apache.giraph.lib.in.text.adjacency-list.LongDoubleDouble
-of org.apache.giraph.lib.out.text.adjacency-list.LongDoubleDouble{noformat}
This wouldn't work with every algorithm, but would be useful in a large
number of cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GIRAPH-64) Create VertexRunner to make it easier to run users' computations
[
https://issues.apache.org/jira/browse/GIRAPH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148943#comment-13148943
]
jirapos...@reviews.apache.org commented on GIRAPH-64:
-
bq. On 2011-11-03 05:32:49, Jake Mannix wrote:
bq. It would be super cool if, like in Mahout and Hadoop, we could print out
the set of Vertex impls / algorithms / actions available. In Mahout, we have a
properties file which we keep updating. Even nicer (maybe?) would be to just
search the classpath for all classes which implement BasicVertex, and list
them. Even cooler: have a new abstract method on BasicVertex String
getHelp() which GiraphRunner could run via reflection to get the help output
for the task.
bq.
bq. Jakob Homan wrote:
bq. Absolutely. Another JIRA?
abstract method or annotation?
Nice thing about annotations is that you can hook into them during compilation
and produce docs...
- Dmitriy
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2700/#review3023
---
On 2011-11-12 02:03:20, Jakob Homan wrote:
bq.
bq. ---
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2700/
bq. ---
bq.
bq. (Updated 2011-11-12 02:03:20)
bq.
bq.
bq. Review request for giraph.
bq.
bq.
bq. Summary
bq. ---
bq.
bq. create giraphrunner
bq.
bq.
bq. This addresses bug GIRAPH-64.
bq. https://issues.apache.org/jira/browse/GIRAPH-64
bq.
bq.
bq. Diffs
bq. -
bq.
bq./trunk/bin/giraph PRE-CREATION
bq./trunk/pom.xml 1196926
bq./trunk/src/main/assembly/assembly.xml PRE-CREATION
bq./trunk/src/main/java/org/apache/giraph/GiraphRunner.java PRE-CREATION
bq./trunk/src/main/java/org/apache/giraph/graph/GraphMapper.java 1196926
bq.
bq. Diff: https://reviews.apache.org/r/2700/diff
bq.
bq.
bq. Testing
bq. ---
bq.
bq.
bq. Thanks,
bq.
bq. Jakob
bq.
bq.
Create VertexRunner to make it easier to run users' computations
Key: GIRAPH-64
URL: https://issues.apache.org/jira/browse/GIRAPH-64
Project: Giraph
Issue Type: New Feature
Reporter: Jakob Homan
Assignee: Jakob Homan
Attachments: GIRAPH-64-2.patch, GIRAPH-64.patch
Currently, if a user wants to implement a Giraph algorithm by extending
{{Vertex}} they must also write all the boilerplate around the {{Tool}}
interface and bundle it with the Giraph jar (or get Giraph on the classpath
and playing nice with the implementation). For example, what is included in
the PageRankBenchmark and what Kohei has done:
https://github.com/smly/java-Giraph-LabelPropagation It would be better if
we had perhaps a Vertex implementation to be subclassed that already had all
the standard Tooling included such that all one had to run would be (assuming
the Giraph jar was already on the classpath):
{noformat}hadoop jar my-awesome-vertex.jar my.awesome.vertex -i jazz_input -o
jazz_output -if org.apache.giraph.lib.in.text.adjacency-list.LongDoubleDouble
-of org.apache.giraph.lib.out.text.adjacency-list.LongDoubleDouble{noformat}
This wouldn't work with every algorithm, but would be useful in a large
number of cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GIRAPH-64) Create VertexRunner to make it easier to run users' computations
[
https://issues.apache.org/jira/browse/GIRAPH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated GIRAPH-64:
--
Attachment: GIRAPH-64-2.patch
Updated patch for Jake's comments. Outputformat is no longer a required param
(though will open a new JIRA to make it so; defaulting to /dev/null is bad) and
inputpath is correctly used.
Hyunsik: mvn assembly:single (or assembly, but that's been deprecated for
single) won't work since we're defining separate assemblies (either the regular
or fat jar), and no default is provided. I tried adding one, but it generated
basically an empty .tar.gz, which is pretty useless. It might be better to
error out than create an empty file. This will go away once we get rid of the
fatjar.
Avery: I can't reproduce what you saw and I'm a bit confused because the error
is referencing lines 136-150 in GiraphRunner, but that file is only 117 lines
long. Can you try it again with this patch on a fresh checkout?
Create VertexRunner to make it easier to run users' computations
Key: GIRAPH-64
URL: https://issues.apache.org/jira/browse/GIRAPH-64
Project: Giraph
Issue Type: New Feature
Reporter: Jakob Homan
Assignee: Jakob Homan
Attachments: GIRAPH-64-2.patch, GIRAPH-64.patch
Currently, if a user wants to implement a Giraph algorithm by extending
{{Vertex}} they must also write all the boilerplate around the {{Tool}}
interface and bundle it with the Giraph jar (or get Giraph on the classpath
and playing nice with the implementation). For example, what is included in
the PageRankBenchmark and what Kohei has done:
https://github.com/smly/java-Giraph-LabelPropagation It would be better if
we had perhaps a Vertex implementation to be subclassed that already had all
the standard Tooling included such that all one had to run would be (assuming
the Giraph jar was already on the classpath):
{noformat}hadoop jar my-awesome-vertex.jar my.awesome.vertex -i jazz_input -o
jazz_output -if org.apache.giraph.lib.in.text.adjacency-list.LongDoubleDouble
-of org.apache.giraph.lib.out.text.adjacency-list.LongDoubleDouble{noformat}
This wouldn't work with every algorithm, but would be useful in a large
number of cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GIRAPH-13) Port Giraph to YARN
[ https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148972#comment-13148972 ] David Capwell commented on GIRAPH-13: - I would also like to help out. I have forked the project on github and have some code already to start the AM/container 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: Jakob Homan 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
