GiraphWorkerContext now exists and it maintains the local-global state for the batch of vertices being executed. I now state in the documentation the implicit 'worker behind the scenes' and you can now use VertexProgram fields to store local-global state. @dalaro … Giraph traversals are now super fast --- like ridiculously so. Prior to this moment, we had each vertex being its own 'worker' and that is grossly inefficient. Also, now with VertexProgram state, no need for caches and thread local nastiness.
Merge branch 'master' of https://github.com/tinkerpop/tinkerpop3