giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maja Kabiljo (JIRA)" <>
Subject [jira] [Updated] (GIRAPH-504) Create PartitionContext
Date Fri, 08 Feb 2013 01:55:12 GMT


Maja Kabiljo updated GIRAPH-504:

    Attachment: GIRAPH-504.diff

Ok, here is my second take on this. PartitionContext, looks much better now I think. I didn't
even put WorkerContext as a field in PartitionContext, but passed it in as argument in pre/postSuperstep,
so user wouldn't get an idea to use it elsewhere :-) 

Removing access to WorkerContext from compute (if we agree to do it) I'd leave for another
patch since a lot of examples would need to be changed.
> Create PartitionContext
> -----------------------
>                 Key: GIRAPH-504
>                 URL:
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>         Attachments: GIRAPH-504.diff, GIRAPH-504.diff
> Right now we have WorkerContext which is accessible from vertex.compute, but it's not
thread safe - usually if we want to use it with multithreaded computation we have to use synchronization.
Instead we can create a ComputeContext, which is going to have one instance per compute thread.

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:

View raw message