Dmitriy V. Ryaboy commented on GIRAPH-28:

I'd caution against the approach of using a MutatorIterator (that's my name for 
that pattern. Like it? :)).
It's effective, but leads to extremely confusing bugs when people try to do 
things like take the first three edges, etc. Presenting a familiar interface 
but providing a tricky unintuitive implementation is not super friendly to 
developers; I don't think we want people to have to study the API to such an 
extent they have to know these details.

> Introduce new primitive-specific MutableVertex subclasses
> ---------------------------------------------------------
>                 Key: GIRAPH-28
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-28
>             Project: Giraph
>          Issue Type: New Feature
>          Components: graph
>    Affects Versions: 0.70.0
>            Reporter: Jake Mannix
>            Assignee: Jake Mannix
>         Attachments: GIRAPH-28.diff, GIRAPH-28.diff
> As discussed on the list, 
> MutableVertex<LongWritable,DoubleWritable,FloatWritable,DoubleWritable> (for 
> example) could be highly optimized in its memory footprint if the vertex and 
> edge data were held in a form which minimized Java object usage.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to