As Jake mentioned, you can have continous processing by making the
mappers in Giraph stop based on an external condition ( I.e.
Specifically asked to do so ) and one can call voteForHalt() only if
that condition is satisfied.
Additionally, the VertexInputSource can be modified to read it from a
continuous input ( like ActiveMQ or even a port ) potentially outside
On 1/3/12, Sebastian Schelter <s...@apache.org> wrote:
> Hi Prasen,
> Storm is supposed to process a continuous stream of data while Giraph is
> a parallel batch processing platform. I think these are inherently
> different systems and one cannot easily be transformed into the other.
> On 03.01.2012 17:51, prasenjit mukherjee wrote:
>> I have a use case which maps perfectly with the open source
>> implementation of storm ( by twitter team ). I think Giraph can be
>> easily modified to have an implementation simulating storm's use
>> cases. Just curious, if anybody had similar thoughts.
Sent from my mobile device