giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan van der Lugt (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-216) NullWritable as VertexData, EdgeData or MessageData should be allowed
Date Tue, 03 Jul 2012 21:50:34 GMT


Jan van der Lugt commented on GIRAPH-216:

Jakob, could you take another look at this? It's the only patch that's still necessary in
order for our graph language to be compatible with Giraph. Would love to have some people
try it out, as it makes writing graph algorithms much easier. Thanks in advance!
> NullWritable as VertexData, EdgeData or MessageData should be allowed
> ---------------------------------------------------------------------
>                 Key: GIRAPH-216
>                 URL:
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Jan van der Lugt
>            Assignee: Jan van der Lugt
>         Attachments: GIRAPH-216.patch, GIRAPH-216.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> When using NullWritable as VertexData, EdgeData or MessageData, an error occurs. This
happens because the constructor of NullWritable is private, so ReflectionUtils.newInstance()
fails. The solution is checking for NullWritable separately, and then returning NullWritable.get()
instead of a new class. This can save very large amounts of memory, since NullWritable is
a singleton.
> This was reported on the mailing list, but never fixed:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message