[ 
https://issues.apache.org/jira/browse/FLINK-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545059#comment-14545059
 ] 

ASF GitHub Bot commented on FLINK-2012:
---------------------------------------

GitHub user andralungu opened a pull request:

    https://github.com/apache/flink/pull/678

    [FLINK-2012][gelly] Added methods to remove/add multiple edges/vertices

    This pull request provides methods for adding/deleting more than one 
vertex/edge at a time. 
    The addEdges method is overloaded to treat the case when a user wants to 
add an existing set of edges. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/andralungu/flink addVertices

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/678.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 #678
    
----
commit a6f5e98d40bee51552fc32e5d034b397b9b51c58
Author: andralungu <lungu.an...@gmail.com>
Date:   2015-05-15T07:03:35Z

    [FLINK-2012][gelly] Added methods to remove/add multiple edges/vertices

----


> addVertices, addEdges, removeVertices, removeEdges methods
> ----------------------------------------------------------
>
>                 Key: FLINK-2012
>                 URL: https://issues.apache.org/jira/browse/FLINK-2012
>             Project: Flink
>          Issue Type: New Feature
>          Components: Gelly
>    Affects Versions: 0.9
>            Reporter: Andra Lungu
>            Assignee: Andra Lungu
>            Priority: Minor
>
> Currently, Gelly only allows the addition/deletion of one vertex/edge at a 
> time. If a user would want to add two (or more) vertices, he/she would need 
> to add a vertex-> create a new graph; then add another vertex -> another 
> graph etc.  
> It would be nice to also have addVertices, addEdges, removeVertices, 
> removeEdges methods. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to