Currently Memory supports incr, and, or, ... These are great and what people will typically use. However, we should also provide the generalization which is simply Memory.reduce. In this situation, incr, or, and, etc. are just specifications of Memory.reduce.
How would it work?
When memory is initialized in a VertexProgram, it would be like this:
Then ReducingFunction would look like this:
Easy peasy. Note that both Spark and Giraph support such types of function-based reduction in their respective "memory engines." TinkerGraphComputer will, of course, be easy to add this functionality too.
Why do this? For two reasons:
1. We get extra flexibility in Memory.