Great, so I can I base GIRAPH-10 and GIRAPH-47 after this one!

About my use case:

I'm implementing a batch path query engine where the queries are
XPath-like queries. Each query is a stack of conditions, each element
assigned to a depth of the path traversal. A message is a stack.

Not each vertex is a starting vertex for the path traversals, so it
could be nice if at the first superstep the starting vertices could
already have the messages in their inbox. This way the message
processing (and path traversal processing with it) could be fully
transparent (vertices just have to iterate throw messages without
caring about parsing, start vertices etc etc).

Currently, at first superstep, each vertex has to get che query from
the conf, parse it into a stack and discard it afterwards, as soon as
it discovers it is not a starting vertex for a path traversal.
Outside, I know who's a starting vertex and could just set the inbox
for those vertices accordingly.

Hope this helps,

On Wed, Nov 2, 2011 at 9:14 AM, Jake Mannix (Commented) (JIRA)
<> wrote:
>    [ 
>  ]
> Jake Mannix commented on GIRAPH-36:
> -----------------------------------
> Excellent, looks good to me.
> +1 for committing we can iterate from here is the main point.  The sooner 
> this gets in, the fewer other patches out there get broken. ;)
>> Ensure that subclassing BasicVertex is possible by user apps
>> ------------------------------------------------------------
>>                 Key: GIRAPH-36
>>                 URL:
>>             Project: Giraph
>>          Issue Type: Improvement
>>          Components: graph
>>    Affects Versions: 0.70.0
>>            Reporter: Jake Mannix
>>            Assignee: Jake Mannix
>>            Priority: Blocker
>>             Fix For: 0.70.0
>>         Attachments: GIRAPH-36.diff, GIRAPH-36.diff, GIRAPH-36.diff, 
>> GIRAPH-36.diff.warnings
>> Original assumptions in Giraph were that all users would subclass Vertex 
>> (which extended MutableVertex extended BasicVertex).  Classes which wish to 
>> have application specific data structures (ie. not a TreeMap<I, Edge<I,E>>) 
>> may need to extend either MutableVertex or BasicVertex.  Unfortunately 
>> VertexRange extends ArrayList<Vertex>, and there are other places where the 
>> assumption is that vertex classes are either Vertex, or at least 
>> MutableVertex.
>> Let's make sure the internal APIs allow for BasicVertex to be the base class.
> --
> 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:

    Claudio Martella

Reply via email to