[ https://issues.apache.org/jira/browse/FLINK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065146#comment-16065146 ]
ASF GitHub Bot commented on FLINK-7006: --------------------------------------- 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. ---- > Base class using POJOs for Gelly algorithms > ------------------------------------------- > > Key: FLINK-7006 > URL: https://issues.apache.org/jira/browse/FLINK-7006 > Project: Flink > Issue Type: Sub-task > Components: Gelly > Affects Versions: 1.4.0 > Reporter: Greg Hogan > Assignee: Greg Hogan > Priority: Minor > Fix For: 1.4.0 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)