[
https://issues.apache.org/jira/browse/GIRAPH-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626942#comment-13626942
]
Claudio Martella commented on GIRAPH-613:
-----------------------------------------
As a matter of fact, you're right, we should not allow at all the user to touch
that part. I started it like that to make it a softer transition, but the more
I think of it (and the more of you agree), the more I think it should not be
possible completely.
One example why I want to introduce this is that it would allow us to take
control of the serialization and avoid writing back edges in the out-of-core
partitions for computations where the adjacencies don't change, with support of
a user parameter (giraph.StaticGraph). As most of the algorithms and analytics
out there do not mutate the graph, it would be a big win.
Does this make more sense now? If I have your +1, I'll remove the possibility
for the user to implement his own VertexWritable class.
I like what you propose, it would also save A LOT OF MEMORY.
> Remove Writable from the interfaces implemented by Vertex
> ---------------------------------------------------------
>
> Key: GIRAPH-613
> URL: https://issues.apache.org/jira/browse/GIRAPH-613
> Project: Giraph
> Issue Type: Improvement
> Reporter: Claudio Martella
> Priority: Minor
> Attachments: NonWritable.diff
>
>
> Currently, Vertex implements Writable, meaning that we depend on the user
> (except for the default implementation) on the way the graph is serialised
> and deserialized. This means we cannot do certain optimisations, and the user
> can actually add additional stuff to Vertex more than Value, Id, Edges and
> halt state. By removing this possibility (or allowing them to extend a
> default implementation) we take control of this.
--
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
