Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3434
Thanks for the review @vasia. The Unary/Binary/TertiaryResult interfaces
will allow follow-on algorithms to work with POJOs or non-conforming Tuples
(where we don't assume source and target vertices are fields 0 and 1). A common
AnalyticResult interface is helpful with drivers that store both directed and
undirected results.
The improvements to the library methods docs do reflect an expectation of
this PR.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
