Are you referring to org.apache.hama.bsp.PartitionRunner ? I don't see a commit removing the class. PartitionRunner is designed to be a Hama job in itself to create the expected splits before starting the submitted job. You can use your own Partitioner in the config using "bsp.input.partitioner.class" . Hopefully I answered your question.
I am trying to make things backward compatible[ HAMA-700 ], but facing some problems. The goal is to have runtime partitioning of graphs done by PartitionRunner itself. -Suraj On Sun, Jan 6, 2013 at 9:54 AM, Apurv Verma <[email protected]> wrote: > Hey all, > I found that PartitioningRunner has been removed from the codepath, I > guess this is the right way to make jobs faster. > But in the current scenario is it possible to have something all > follows. I want that all values < some integer are designated to peer > index 0, all values in range 0-a to peer index 1, and so on and so > forth. > With the partitioning removed would i need to use an additional > superstep to do this classification of input records. > > > -- > Regards, > Apurv Verma >
