Hi Martin, it depends on the details of your implementation. In principle, you do not write Mapper and Reducer classes, which are tested by MR-Unit. You usually have to implement the application / algorithm specific logic, in e.g. the Vertex class. MR-Unit might not help that much here.
This leads to the question, if there is a comparable approach / or tool like MR Unit for Giraph? Best wishes Mirko On Tue, Feb 18, 2014 at 3:52 PM, Martin Neumann <mneum...@spotify.com>wrote: > How much of the Giraph 1.1.0 version is still based on MapReduce? > Would something like mrunit (http://mrunit.apache.org/) work with it? > > > On Tue, Feb 18, 2014 at 12:52 PM, Martin Neumann <mneum...@spotify.com>wrote: > >> I'm using the Yarn version (1.1.0 trunk) and I was not able to get it to >> work that way. But I'm no expert on that, if anyone knows a way to get it >> done It would be great. >> >> >> On Tue, Feb 18, 2014 at 2:07 AM, Roman Shaposhnik >> <ro...@shaposhnik.org>wrote: >> >>> I find running Giraph apps via hadoop's local execution mode >>> quite useful for debugging. >>> >>> Thanks, >>> Roman. >>> >>> On Mon, Feb 17, 2014 at 4:07 AM, Martin Neumann <mneum...@spotify.com> >>> wrote: >>> > Hej, >>> > >>> > I find Giraph programs quite difficult to debug (all I have is log >>> outputs). >>> > Anyone has some hints for debugging tools or coding practices to make >>> it >>> > simpler? >>> > >>> > I'm using Giraph 1.1.0 trunk on YARN so I can't use Map/Reduce >>> debugging >>> > aids (at least I think so, I haven't tried any) >>> > >>> > cheers >>> > Martin >>> >> >> >
