[
https://issues.apache.org/jira/browse/FLINK-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259793#comment-15259793
]
ASF GitHub Bot commented on FLINK-3771:
---------------------------------------
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/1900#issuecomment-215012658
How about we add the translate methods to the `Graph` class and implement
translators as `MapFunction<Old, New>`? This way they can be used even if don't
have a graph but a dataset of vertices or edges. There is no requirement to
have the mappers operate on the vertex and edge level.
Does this sound like a good idea?
> Methods for translating Graphs
> ------------------------------
>
> Key: FLINK-3771
> URL: https://issues.apache.org/jira/browse/FLINK-3771
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Fix For: 1.1.0
>
>
> Provide methods for translation of the type or value of graph labels, vertex
> values, and edge values.
> Sample use cases:
> * shifting graph labels in order to union generated graphs or graphs read
> from multiple sources
> * downsizing labels or values since algorithms prefer to generate wide types
> which may be expensive for further computation
> * changing label type for testing or benchmarking alternative code paths
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
