flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-2857) Gelly API improvements
Date Mon, 19 Oct 2015 16:09:05 GMT

     [ https://issues.apache.org/jira/browse/FLINK-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Fabian Hueske closed FLINK-2857.
       Resolution: Fixed
    Fix Version/s: 0.10

Implemented with 640e63beef0b60891178affc7a6e8f0d01a5d000

> Gelly API improvements
> ----------------------
>                 Key: FLINK-2857
>                 URL: https://issues.apache.org/jira/browse/FLINK-2857
>             Project: Flink
>          Issue Type: Improvement
>          Components: Gelly
>            Reporter: Vasia Kalavri
>            Assignee: Vasia Kalavri
>             Fix For: 0.10
> During the Flink Forward Gelly School training, I got some really valuable feedback from
participants on what they found hard to grasp or non-intuitive in the API. 
> Based on that, I propose we make the following improvements:
> -  rename the mapper in creation methods to {{VertexInitializer}}, so that its purpose
is easier to understand.
> - add a {{fromTuple2DataSet}} method to easily create graphs from {{Tuple2}} datasets,
i.e. edges with no values.
> - in {{joinWith*}} methods, it is hard to understand what are the parameters in the mapper
and what will be the output. I suggest we flatten them, try to give intuitive names and improve
the javadocs.
> - in neighborhood methods, it is hard to understand what are the arguments of the {{EdgeFunction.iterateEdges}}
and {{ReduceEdgesFunction.reduceEdges}}. Javadocs and parameter names could be improved here

This message was sent by Atlassian JIRA

View raw message