Description
Excerpt from the mailing list:
I would like to add a setup(BSPPeer peer) and a cleanup(BSPPeer peer) method to our abstract BSP class.
In addition I want to implement the setConfiguration and getConfiguration in our abstract BSP class, add a Configuration field, and set them to deprecated. (maybe we can remove them in our 5.0 release).
To retrieve the job's configuration, the user should use peer.getConfiguration().
Similar to the Hadoop flow, we are executing setup->bsp->cleanup.
Maybe we can refactor our examples to match this new possibility.