Jake Mannix commented on GIRAPH-28:

ah, yes.  That can be a nasty pit of snakes for new developers, no matter how 
commonly it's found in Hadoop-land.

So I'll put in my vote for Iterable<I>, with your offline suggestion of boolean 
hasSortedIterator() (defaulting in BasicVertex to "return true;", overrideable 
in subclasses).

And I'll put in a patch on GIRAPH-31 so my code'll be where my mouth is (and we 
can continue this discussion on a ticket with a shorter thread [so far]).

> 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