Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/537#issuecomment-87425953
Hi @vasia ,
1). I will add the documentation once we reach a consensus. No use
documenting something that might change :)
2). For the public setter: I still couldn't think of a workaround. Waiting
for suggestions.
3). Most of the comments were addressed in this final commit, however, when
speaking about avoiding unnecessary overhead, the only way I could do that is
to add another VertexCentricIteration class that operates on Tuple3 and have
the user decide from the constructor which class he/she wants to use. To me
that seems to introduce a ton of duplicate code which will look very bad.
Keeping in mind that I need to store the degrees in the vertex value, any
suggestions on how to eliminate this overhead would be very useful.
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
