[
https://issues.apache.org/jira/browse/FLINK-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900050#comment-14900050
]
ASF GitHub Bot commented on FLINK-2663:
---------------------------------------
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/1152
[FLINK-2663] [gelly] Changes library methods to use generic keys
This PR updates the Gelly library methods to use generic vertex keys and
values where possible.
It also adds missing Javadocs to the Gather-Sum-Apply classes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vasia/flink flink-2663
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1152.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 #1152
----
commit da14718d5b40da450edcacd1f20dd088906f5498
Author: vasia <[email protected]>
Date: 2015-09-20T19:20:11Z
[FLINK-2663] [gelly] Updated Gelly library methods to use generic key types
commit 2bed8de829abdafedbffc8af932a56397eb4ad46
Author: vasia <[email protected]>
Date: 2015-09-20T19:21:04Z
[gelly] Added missing Javadocs to GSA classes
commit 4d2fad311fa5fd0f6f19a5d8b9eed4c36b75a4cc
Author: vasia <[email protected]>
Date: 2015-09-20T19:47:39Z
[FLINK-2663] [gelly] Updated Gelly library methods to also use generic
vertex/edge values where possible
----
> Update Gelly library methods to use any key type
> ------------------------------------------------
>
> Key: FLINK-2663
> URL: https://issues.apache.org/jira/browse/FLINK-2663
> Project: Flink
> Issue Type: Improvement
> Components: Gelly
> Reporter: Vasia Kalavri
> Assignee: Vasia Kalavri
>
> Several Gelly library methods assume a certain key/value type even if not
> really necessary. For example, CommunityDetection assumes Long vertex keys
> and values, ConnectedComponents assumes Long keys, etc.
> We should update the Gelly library methods to use any key type and
> vertex/edge value types when possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
