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

Anastasis Andronidis updated HAMA-767:
--------------------------------------

    Attachment: HAMA-767-addAndRemove-v1.patch

I added remove functionality. I also altered interfaces of VertexInfo and 
VertexInterface. 

In ListVerticesInfo I implemented a remove method which is using binary search 
on vertexes. On the other hand, I didn't implement the same method in 
DiskVerticesInfo, because it was a little bit complex (I will try to implement 
it later).

I have some questions though:
1) I have some concerns about the partitioner. At this point, the partitioner 
will always return to me correct peer. But the case is not the same if we have 
a random or probabilistic partitioner. Should I keep in mind a use case like 
that?
2) When I delete a vertex, should I return their value and edges? (To do that 
the deleted vertex will have to send a message on the next super step, and I 
believe that will be confusing).
3) On ListVertecesInfo interface, we will have to force implement a remove 
method. I want to also enforce this method to return an exception when the 
vertex is not there. Which is the exception that will match the best? Currently 
I'm using UnsupportedOperationException.
                
> [GSoC 2013] Vertex addition and removal
> ---------------------------------------
>
>                 Key: HAMA-767
>                 URL: https://issues.apache.org/jira/browse/HAMA-767
>             Project: Hama
>          Issue Type: New Feature
>          Components: examples, graph
>    Affects Versions: 0.6.1
>            Reporter: Anastasis Andronidis
>            Assignee: Anastasis Andronidis
>              Labels: dynamic, graph, gsoc, gsoc2013, mentoring
>             Fix For: 0.6.3
>
>         Attachments: HAMA-767-addAndRemove-v1.patch, 
> HAMA-767-addition-v1.patch
>
>
> Implement addVertex and removeVertex methods for incremental graph support on 
> Graph API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to