GitHub user greghogan opened a pull request: https://github.com/apache/flink/pull/4201
[FLINK-7006] [gelly] Base class using POJOs for Gelly algorithms Gelly algorithms commonly have a Result class extending a Tuple type and implementing one of the Unary/Binary/TertiaryResult interfaces. Add a Unary/Binary/TertiaryResultBase class implementing each interface and convert the Result classes to POJOs extending the base result classes. Note: The `TriangleListing` hashes changed because previously these algorithms did not have a `Result` class and simply used the `Tuple` `hashCode`. You can merge this pull request into a Git repository by running: $ git pull https://github.com/greghogan/flink 7006_base_class_using_pojos_for_gelly_algorithms Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/4201.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4201 ---- commit 15ac62ba7d0f7982961aa4b631870a641510c707 Author: Greg Hogan <c...@greghogan.com> Date: 2017-06-26T14:21:50Z [FLINK-7006] [gelly] Base class using POJOs for Gelly algorithms Gelly algorithms commonly have a Result class extending a Tuple type and implementing one of the Unary/Binary/TertiaryResult interfaces. Add a Unary/Binary/TertiaryResultBase class implementing each interface and convert the Result classes to POJOs extending the base result classes. ---- --- 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. ---